I mean...this depends very heavily on what the purpose of the writing is.
If it's to succinctly communicate key facts, then you write it quickly.
- Discovered that Bilbo's old ring is, in fact, the One Ring of Power.
- Took it on a journey southward to Mordor.
- Experienced a bunch of hardship along the way, and nearly failed at the end, but with Sméagol's contribution, successfully destroyed the Ring and defeated Sauron forever.
....And if it's to tell a story, then you write The Lord of the Rings.
Now, that's very true! But it's a far cry from implying that all or most humanities teachers are all about writing florid essays when 3 bullet points will do.
Not to explain away Ikea's byzantine system, a difference in size usually comes with a difference in use and environment.
While a T-shirt has the same purpose in S M or L, a table isn't the same if it's lower smaller than 50cm or longer than 1.5m, or lower than 60cm or higher than 70cm. In a standard shop you'd call that a night stand, or a coffee table, or a kids' table or living room's low table etc.
If you think of it as shopping for an environment (same as half of the in-shop experience: they'll show you full rooms where you can see products fit together) it makes sense. Somewhat.
I agree that for tables there can be a difference in use but when IKEA has a dresser series named "HEMNES bedroom series" then that argument kind of goes out of the window.
It's not super hard to back up (using the "bread crumbs" on the page you linked), to "Dressers & chests of drawers", pop down the "Series" input selector, and pick STORKLINTA. That gets you [1] which I hope shows all the dressers of that name.
Please look at it quickly and try understanding what elements are available.
Or, say, Platsa having half of the pieces called Småstad, because they kinda would also fit in kid's room. Or trying to find codenames for doors/facades/drawers of Metod or Pax.
I didn't see the filter because it is only shown for wide windows (over 1250px wide) or when clicking the "All filters" button and is then at the bottom of the list.
The list even isn't sorted and looks like a SELECT without order from a database.
It is really odd they don't have a (sub) category page for each of the series.
"In case users prefer native decoding speed over Wasm, F3 plans to offer an option to associate a URL with each Wasm binary, pointing to source code or a precompiled library."
They are not suggesting that the code at the url would be automatically downloaded. It would be up to you to get the code and build it into your application like any other library.
Is this relevant in practice? Say I go to a website to download some data, but a malicious actor has injected an evil decoder (that does what exactly?). They could just have injected the wasm into the website I am visiting to get the data!
In fact, wasm was explicitly designed for me to run unverified wasm blobs from random sources safely on my computer.
> A doctor who has a diploma is much more likely to be a useful/good doctor than a person with a "computer science" diploma will be a good developer.
A few things to consider:
What we practice is "software engineering." Computer science is closely related to software engineering; but not the same thing. (It's like the difference between a degree in physics vs mechanical engineering.)
Doctors still have to be board certified, which requires self-study of topics that aren't taught in class. Some people do get their medical diploma and fail their board certifications, in which case they can't practice.
I should add: One of things, for doctors, that board certification does is make sure that doctors know topics that aren't covered in school.
My computer science degree overlooked a lot of topics that are very important when developing an industrial strength application; specifically, an application that is not an academic exercise, which gets back to:
> A doctor who has a diploma is much more likely to be a useful/good doctor than a person with a "computer science" diploma will be a good developer.
If we, as an industry, had something similar to doctors getting board certified, we could put pressure on ourselves (and academic institutions) to make sure that ample opportunity is provided in schools to learn how to be a good developer.
Back when I started, I think maybe half of the people I worked with had a relevant degree at most. Even that might be an overestimate.
Back then, CS degree programs didn't even teach higher level languages than C/++ as they were thought to change too quickly. Whatever you learned during your four years wouldn't apply after you graduated. Instead, the programs focused on the low level implementation details with the theory that was where the engineering and science were.
Now, the same school I went to has courses and tracks for web technologies, so who knows.
This way they could keep an old html/css/js implementation running alongside the upgraded one.