AMD employee by Ciro Santilli 35 Updated +Created
ATI Technologies by Ciro Santilli 35 Updated +Created
AMD Instinct by Ciro Santilli 35 Updated +Created
Radeon by Ciro Santilli 35 Updated +Created
We have to distinguish between two types of creations. We'll discuss how the cost of coming up with both can be recouped without intellectual property and its awfulness.
Figure 1. Ancient problems require modern solutions.
All claimed land will be privately owned; patronize places (neighbourhoods, restaurants, streets, beaches, parks, etc.) which implement the rules that you want. Such places also have an incentive to enforce said rules to not just attract but keep their target customers.
AMDGPU by Ciro Santilli 35 Updated +Created
Ryzen by Ciro Santilli 35 Updated +Created
This was the CPU architecure that saved AMD in the 2010's, see also: Video "How AMD went from nearly Bankrupt to Booming by Brandon Yen (2021)"
If your pollution damages the property of others, that would violate the NAP, and a minarchy would be justified in collecting penalties for the same and distributing them to the people affected. This should incentivize the company to try and prevent or clean up its pollution as much as possible. We need to decide the extent of such penalties, and whether penalties other than monetary ones would be even more effective at preventing pollution.
Insider trading can discourage investment, and cause CEOs to hide information from employees. While there have been arguments that insider trading makes share prices more quickly go to their proper value, the true solution is that if investors dislike insider trading, companies can legally declare that they will only work with those that legally agree not to trade its shares or facilitate insider trading. If someone unaffiliated with the company simply overhears or comes across insider information, this won't stop them, but even if it were illegal, it would be nearly impossible to prove such a case.
That the person you're about to attack may have a gun on them will deter the majority of attackers. If nobody had guns, only melee weapons, it would be easy for a group to attack someone, say with baseball bats, etc., suffer little to no injury themselves, and get away. If everyone has a gun, you can ambush someone on the street, but will likely get killed by bystander. If you target someone in a location where they see/hear you coming, like their home or workplace, the attackers will suffer more harm than the "victim". This is more effective deterrent and solution to attacks than the police, who can almost always arrive only after the crime is over.
In countries with gun rights, like the US, the chance of someone not involved in crime being killed in a shooting is very low, and the number of victims in suicidal mass shootings can be minimized if even more bystanders have guns. It is unfortunate that it is impossible to quantify the number of attacks/muggings that never happened because the possibility of people being armed stopped them. This number is almost certainly huge.
Moreover, one otherwise cannot guarantee that the government will never ever turn tyrannical. An armed populace almost certainly can.
In a free market, the one who provides a good/service for the lowest price gets nearly all the customers. The one offering the highest for the same job gets nearly all the employees. No one wants to let another do this and dominate the industry, so they all compete against each other for customers and employees. Employees can also form unions to demand payment almost equal to the value they bring.
Raspberry Pi Pico W UART by Ciro Santilli 35 Updated +Created
You can connect form an Ubuntu 22.04 host as:
screen /dev/ttyACM0 115200
When in screen, you can Ctrl + C to kill main.py, and then execution stops and you are left in a Python shell. From there:
  • Ctrl + D: reboots
  • Ctrl + A K: kills the GNU screen window. Execution continues normally
but be aware of: Raspberry Pi Pico W freezes a few seconds after after screen disconnects from UART.
Raspberry Pi 3 by Ciro Santilli 35 Updated +Created
Model B V 1.2.
SoC: BCM2837
Serial from cat /proc/cpuinfo: 00000000c77ddb77
Raspberry Pi by Ciro Santilli 35 Updated +Created
Lenovo by Ciro Santilli 35 Updated +Created
Their websites a bit shitty, clearly a non cohesive amalgamation of several different groups.
E.g. you have to create several separate accounts, and different regions have completely different accounts and websites.
The Europe replacement part website for example is clearly made by a third party called flex.com/ and has Flex written all over it, and the header of the home page has a slightly broken but very obviously broken CSS. And you can't create an account without a VAT number... and they confirmed by email that they don't sell to non-corporate entities without a VAT number. What a bullshit!
Pinned article: ourbigbook/introduction-to-the-ourbigbook-project
Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
Video 1.
Intro to OurBigBook
. Source.
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
    Video 2.
    OurBigBook Web topics demo
    . Source.
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    • to OurBigBook.com to get awesome multi-user features like topics and likes
    • as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 5. . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
    Video 4.
    OurBigBook Visual Studio Code extension editing and navigation demo
    . Source.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact