I will try to remember him for his far too relatable Dilbert comics about corporate office life, and not his, uhm, later work.
One of my favorite strips was Dilbert in the 90s only being given a 286 PC for 3D rendering work, with the boss saying "besides, how often will you do 3D rendering in your career?"
Safari team explicitly targets perf as a target. I just wish they weren't so bad about extensions and adblock and I'd use it as my daily driver. But those paper cuts make me go back to chromium browsers all the time.
I was just helping out with the network at an event. Worked great in testing, but it failed in production due to unicast flooding the network core. Turns out that some of the PoE Ethernet switches had an insufficiently sized CAM for the deployment combined with STP topology changes reducing the effective size of the CAM by a factor of 10 on the larger switches. Gotta love when packet forwarding goes from O(1) to O(n) and O(n^2)! Debugging that in production is non-trivial as the needle is in such a large haystack of packets so as to be nearly impossible to find in the output of tcpdump and wireshark. The horror... The horror...
First big project I worked on a couple of us sped up the db initialization scripts so we could use a less trivial set of test data to stop this sort of shenanigans.
Things like inserting the test data first and turning on constraints and possibly indexes afterward.
My bad. I had been reading about how there's a frustration in the community that allistic people refuse to explain why such statements are wrong, and instead just repeat "you know what you did!" to people who genuinely don't.
I tried to be the one who didn't do that, but missed the mark. I'd delete it if I could.
Only 1% of the population has autism. Presenting autism as a considerable possibility for trollish behavior isn't much different than what the parent commenter did.
Is there more context to this question? I couldn't read the article because of the pay wall. But in isolation, this is a dumb question. All decent parents want their child to live as long as possible and be as healthy as possible. Is there something deeper you were trying to get at?
So what? So a father shouldn't celebrate medical advances that mean their kid doesn't have to die after a week? And if it does, they should just be like "Ah, that's life!"
Oh, sorry. I definitely think a father can (should?) celebrate medical advancements like this, and definitely shouldn't undermine death like "Ah, that's life". My point is that people often worry about their children's death when they themselves are still alive. Death seems okay if it's when they don't get to see it
You are trying to frame this as pure “logic” but if you had read a single book on ethics or even philosophy you would see that’s not the case. You are basically asking “but why is good better than bad?” Acting as if you are logical but failing basic premises of logic or ethics. Any ethical framework is going to have axioms, typicslly these axioms are things that are inarguable for any person, namely its better to live than die, or to reduce suffering, etc. using basically any ethics system and pure logic you will quickly reach a conclusion that a baby living is better than one dying.
This really has nothing to do with the inevitability of death. Death is inevitable, however there is a difference between a child dying and an elderly person dying. A child has potential, they have not lived their lives. A child has not actually lived the full basic human experience, they havent had a crush, or fallen in love or married or had children or had any great successes or failures or close friends or anything, these things everyone does. An older person has, they are not a pure soul who hasnt experienced life. After 70 years you can be sad for the individual passing but happy that they have experienced life. This is why when a parent has a child they arent sad that their child will die in 80 years, but are devasted if they die at a week. The child never even had a chance. When you actually have a child, its an emotional and fulfilling experience, and to have that torn out so early is damaging.
From an empathy and emotional pov these things are so extemely basic and foundational aspects of being a human, a 10 year old from any culture on earth can undersrand this with no difficulty. And any person with even a passing familiarty with logic, ethics or philosophy will dismiss you as being earnest. Which is why people are assuming you are a troll.
A parent's obligation is to try and do everything they can to make their child's life good. I think most people would agree that living more than a week is a good thing.
> If it's difficult to find kernel developers then wouldn't it help to not require them to also know web UX?
That means hiring two people, and in $current_year, companies expect one person to know everything. Sysadmin, backend programmer, frontend programmer, designer and a DBA used to be different people not that long ago, now they expect one person to do all that... + it seems they want kernel development experience now.
Sure, some C code, some html, a table here, a colspan there, and you can have a website made by a single person... if we want a website to look like it was made on an 1980s computer by a single person.
If you're not that person, it's fine. Some people still just use notepad and write html like it's 1999. Other have both kernel experience, and have picked up react at some point in the past ten years. Plus LLMs write css these days, so no colspan needed.
At the rate LLMs are improving, that certainly seems like a possibility, but until they do, why would you need one for that? Kernel C makes sense. CSS is the problem here.
Or, you can have a decent website made by a single person. It's not that hard to learn basic HTML5, enough ARIA semantics to know not to use ARIA, a programming language with decent synchronisation primitives that supports CGI, an SQL dialect and the principles of relational database design, enough JavaScript to use MDN, enough CSS to use MDN, the basics of server maintenance, TLS certificate provision, and DNS.
If you want to do your own networking, or run email, that's a whole 'nother specialism; but just running a website is easy enough for one person to do.
Good, that's the way it was until the splitting of roles for commodification. A programmer is more like the Renaissance man who makes it a goal to do everything from different disciplines than a drone who has been trained to do one thing and can only be trusted to do one thing.
It's not commodification, it's acknoledging that tech got exponentially more complex over the decades.
just think of your favorite video game character in 2000 and then one in the 2020's and consider how much tech is needed to render, animate, light, and conceptualize it. in 2000 this was all done by maybe one artist and one gamedev, probably making a character with some hundreds of polys at best. now that artist has a pipeline of riggers, material artists, animators, and concept artists, while that single dev became a graphics programmer, gameplay programmer, tech artist, and build engineer.
My point was unnecessarily they split the roles. An artist can cover concept and materials. A programmer can do gameplay, graphics, rendering and builds. In fact having people who understand the entire project makes for a better project.
It's like moving from custom built cars to the assembly line where someone's job is putting in one screw. I understand it's cheaper/faster because you can hire anyone unskilled for cheap but cars were all suppose to be identical. Software should be unique (if not just copy the last thing built) but I guess when it comes to major games things are more of factory throwing millions of pixels of characters at existing game engines while copying gameplay of successful games. That's why games are shovelware these days like a netflix original.
But we now expect a single person to design the engine, the bodywork, both aesthetically and technically, make an engine, actually make all those parts, assemble them together, pain the car and test it.
Jack of all trades, master of none. This is why we need clusters, "stacks" and "clouds" on the server side and gigabytes of ram on the client side + many megabytes transfered, just to show one simple weather forecast website that gives the user the same amount of information as a WAP site did on a five line mobile phone back in GPRS times.
Sure, let me explain it a bit better. It's more like in the sense of the "stack" is very deep now. Clearly, we have/hire Xen/hypervisors specialist, and we do not ask them to be CSS experts. However, deeper in the stack (at lower levels) harder it is to find them, because of the lack of expertise in universities and/or appeal of doing such job.
And if you find or train those low-level/system-oriented people, they also need to understand how a feature they build will be exposed functionally to a user (and why they need it in the first place). Because things are not make into thin-air but required to work in a bigger picture (ie: the product).
It feels like we're back in 1900 when anyone's clever idea (and implementation) can give huge performance improvements, such as Ford's assembly line and Taylor's scientific management of optimizing shovel sizes for coal.
yes, it also feels like we are going to lose our just-in-time global shipments of anything to anywhere any day now. It will soon feel like 1900 in other ways.
I'm surprised there are no UTF-8 specific decode instructions yet, the way ARM has "FJCVTZS - Floating-point Javascript Convert to Signed fixed-point, rounding toward Zero"
FJCVTZS isn't really as specific to Javascript as the name suggests, it actually copies the semantics of an x86 instruction, which JS took its semantics from.
JS runtimes do use it but it's useful anywhere you need to do what x86 does, which obviously includes running x86 binaries under emulation.
One of my favorite strips was Dilbert in the 90s only being given a 286 PC for 3D rendering work, with the boss saying "besides, how often will you do 3D rendering in your career?"
Dilbert replies "Once, if I hurry"