It's not a race to the top of the safety spectrum. That's just a disguise and also only for some people. It's a race to the top of the "social" and $ spectrum where you have to show how little you care about the others and the environment and also how much money you can dump on vanity and impractical things
I think it's actually both. Some people buy bigger cars for looks/status, and then others (esp. parents of small children) feel compelled to buy a larger, safer vehicle in response. In the case of minivans, they are choosing a less cool, but safer, vehicle than smaller alternatives.
Occupants of the largest vehicles on the road experience less than 1/10 of the fatalities than those in the smallest. We desperately need new regulations/legislation to address the vehicle size arms race.
It's a bad practice always since the user can easily choose if he/she wants to open it in new tab by themselv but not the other way. For a user there is zero benefits in this practice
"The user" on a typical website does not know how to do this.
For a user there is the benefit that they will not lose their presence on the website. Many users do not know how to navigate back.
Of course, in times long gone a new window would appear, and the pattern made even more sense than with tabs.
If you would have left out the word "always", I might have agreed that for this particular website and intended audience, it does not make much of a difference.
When i was around 20 i learned Ruby as basically my first language and it has been a joyride ever since. I had a chance to develop and co-develop things in other languages but for me there is none matching speed, joy and effectivity of Ruby.
Everyone's mileage may vary but i definitelly do recommend learnign Ruby as a first leanguage. What i also recommend starting developers is to not follow dogmatic advices blindly.
Same with PHP: its bad reputation was due the proliferation of terrible, insecure and unmaintainable code written by first time programmers (or should I say webmasters) in the early 2000s.
These days its Javascript and the horde of fresh faced web designers and React engineers that try and reinvent the wheel. I don't think the quality of JS engineers on average is that low, programming culture has improved a lot, but without real world experience one tends to both overengineer and underestimate the problem. The JS world is very brittle because of it, and because of a frankly terrible language.
Can you be more specific? I'v been working with accounting systems for some time also and there are no transactions in double entry accounting which "just don't need the other side".
I don't get how the author can value all the things in the article and yet work at Microsoft on a bloatware like Edge which is not possible to remove, is pushed hard by Windows against other browsers and used as a part of a giant ads engine in itself
It's not bizarre if you realize that the decisions are not really in your hands. You are an engineer working in martech, you do what your company tells you to do and your company is motivated by profit, especially in martech. When your bosses decide it's time to start doing that, you will follow and if not, plenty of other engineers will. It's not like there are not dozens and dozens of examples of companies doing exactly that
Except that from my own experience connecting to EDI needs more custom programming than connecting to RESt APIs. The format is horrible and also the whole workflow based around sending and receiving messages
