The settlement does not follow a mere claim, here you have a court that inflicted punitive damage to Tesla after a trial.
Also most business are not racist nor hostile to the extent Tesla is described by the victims, otherwise they would indeed be shut down.
Your cameras and microphones argument makes no sense. Racist graffitis in the restroom does not require big brother level of surveillance for the company to start an internal investigation.
Also mandatory arbitration agreements is obviously used to avoid both dealing with toxic behavior inside the company and public backlash.
I spent two years with threejs then the last 2 years with Babylon.js
Three.js has a huge community, learning 3D programming by learning three.js from the community is very feasible, lots of nice exemples around.
Babylon.js is maintained by a team of Microsoft employees. It is a cohesive piece of software with tons of integrated utilities (controls, GUI, good debugging tools, an excellent jsfiddle equivalent called playground etc).
It is the perfect balance between a rendering and a game engine.
Also it has a well engineered Typescript codebase that in my humble experience has been more stable than Three.
The docs are great, the community is nice and super active, contributing is easy but you have much less online exemples than with Three.
So my advice for a 3D novice would be to play with Three.js and see where it goes. If you are in it for art and making things look good, the amount of examples with Three will also help a lot.
Now if you value engineering, and you already have even a very modest experience with 3D programming I really recommend Babylon.js
Also you will see Aframe, react-fiber or react-babylon thrown around: don't bother if you don't already know Three or Babylon. You will outgrow them and still have to learn Three/Babylon "the correct way". I think that most people decent with Three or Babylon can make their own specific abstraction with less overhead anyway.
A lot of businesses publish apps on the App Store because it is the only option Apple gives consumers to install their app.
You are most likely not going to be discovered just by being on a Store but rather through your online presence.
In a free world you could own your app distribution logistics with the cloud provider you already have to use for your app, website or for other part of your business. You can do it on Windows it didn't kill Microsoft business at all
The issue is not Apple making a profit on its store. Selling phones is unrelated to owning a store, they have one good for them but why is it mandatory to access such a huge share of the mobile market ?
What value is given to businesses and developers, and what undue avantages over competition Apple gets by tying both together ?
Now let's admit you do want to be on their store. Now you want to take payments, your bank has tech to take payments, Stripe has tech to take payments, PayPal does to etc. Apple want to compete with those with their In App Purchase tech fine but there has to be choice. The cut is 30% because they forbid competition in payments. They forbid even mentioning to customers they can have a better deal outside.
If Apple thinks being on the App Store is such a privilege it should either :
- Make businesses & developers pay for being on it and let them chose their payment provider
- Keep on bundling phones with a store where their payment tech is mandatory but let customers install apps that are not from the App Store
They can fight it as hard as they want the EU regulators will make them do that choice anyway because the anti trust case against them is even sounder than the Microsoft one with Internet Explorer
I didn't assume that dynamic languages are more concise. I only said that each of both (with the addition of interpreted languages) usually require less tooling and less to keep in mind than their respective opposite
How much you need autocomplete and refactoring to be reliable also depends on your situation (language/framework, app structure and number of contributors).
More people use IDEs with dynamic languages because Visual Studio Code now exists so people who always prefered IDEs now have a good option
It depends of the language and/or the stack you use.
Typed, verbose and compiled languages users tends to use an IDE by default because the amount of tooling and things to keep in mind to write executable code is higher than with dynamic, concise and interpreted languages.
People proficient with the latter categories of languages will know what is lacking in their text editor and will extend it with whatever they need (coercive linting, git integration, macros, new layout etc...) on a case to case basis. They end up with a tool that suits their strengths/weaknesses/taste, is faster than IDEs and avoid eventual problems from tools IDEs chose for you.
Chosing a text editor is not about refusing to get help from technology. It is about having a good typing experience first and around it being free to pick the tools you need.
Also, a lot of tools that both IDE and text editor users use (like git integration) do things that can be well done with good command line proficiency. So it really is about your needs
Really it is a debate similar to "Batteries-included frameworks vs multiple librairies" so there is different answers for different situations
Also most business are not racist nor hostile to the extent Tesla is described by the victims, otherwise they would indeed be shut down.
Your cameras and microphones argument makes no sense. Racist graffitis in the restroom does not require big brother level of surveillance for the company to start an internal investigation.
Also mandatory arbitration agreements is obviously used to avoid both dealing with toxic behavior inside the company and public backlash.