As the article notes, that's because CPUs are designed to run existing C code fast. You could create an instruction set that provided this control, but it might be a tough sell in a world full of C code.
YIMBYism simultaneously raises prices (presumably for the greedy developers and sellouts) and lowers them (for the noble neighborhood defenders who are forced to sell). Got it.
I'm going to ignore your presumptions (your "greedy developers and sellouts) and things I did not say (like "YIMBYism lowers prices for noble neighborhood defenders who are forced to sell"), so basically every word and try to find the spirit of your comment.
It's pretty difficult to fit a massive apartment building on a house sized plot between two massive apartment buildings. The prices you will be offered are not what your neighbors were offered. There will also be pressure on you to sell because your neighborhood is now shit. Your house prices may still, all that being considered, have massively risen since you bought the house. The property taxes also rose proportionally, sucking away your equity.
I think the contradictions are pretty clear: it raises prices, but holdouts sell cheap; it's a shit neighborhood that no one wants to live in because it's too crowded...
And the hypothetical boxed-in holdout scenario is simply not representative of what's happening in high demand areas in the US. We're preserving laundromats and parking lots in San Francisco and Manhattan. No one is trying to build towers in the middle of suburbia.
As a layout and rendering toolkit, the modern web browser is just head and shoulders above everything else in terms of features and ease of use.
As problematic as CSS is, getting things in the right place is still dramatically easier than with Swing LayoutManagers, and when you do have problems, you have great tools in the browser to explain what's going on.
Browsers particularly shine in text rendering, naturally; text styling, font selection, word wrapping, etc. are all easily configurable. You want bold text next to regular text in Swing? You either need two JLabels, or you wrap your text in <html> tags and let the embedded HTML 3.2 renderer do it.
Whaaat, no way. Sure, Swing is not the epitome of a framework, but the web was famously terrible before flexbox, and it is still not as advanced as something like Apple’s constraints based layouting system.
Also, word wrapping? HTML is quite terrible to read compared to Latex-rendered text so I wouldn’t say that it is all that good in fonts either.
Swing isn't exactly the latest toolkit though, is it?
JavaFX has much more intuitive layout for apps than HTML and also has CSS. So you can get the best of all worlds. HTML5 has been trying to catch up with CSS flex-box, but it's all just retrofitted and shows.
The built-in version has the big advantage that it integrates well with tools: you can statically determine the target of the reference and jump to it.
The unspoilt countryside can certainly be pleasant, at least for the few that are well-off retired, or don't need access to an urban center to make a decent living, and don't mind driving an hour to do anything.
Start putting McMansions and Applebees in the countryside, and it becomes spoiled rather quickly.
He states that H-M is not used because of the lack of reified generics, which is completely irrelevant. (Hint: type systems perform analysis at compile time; "reified generics" means having type arguments available at run-time.) H-M is not used because it is not compatible with subtyping or method overloading, which are both critical for Java interop. There is no particular reason that Scala needs to use exactly the H-M system.
Do you have any experience with the inverse statement? That is, have you had a good experience with optional types in an enterprise context?
I'm curious how many runtime errors persist due to the optionality of the type system. Perhaps code standards requiring all "library" code to be typed would be a good balance.
Most enterprise customers I have worked with, favour dynamic languages just for scripting tasks, while using static typed ones for the large scale projects.
By large scale, I mean, projects with at least three development sites, at least 30 developers, all the different set of skills. With lots of attrition.
The only time I saw it working, was in a project done with TCL, which lacks optional types, but everyone on team was a top developer, the team was small, and located on the same open space. So startup world, not enterprise.
