bakatubas

Well it’s hard to say at the scope of world powers. Maybe small, local governments there’s less. But let’s be honest here, and consider the atrocities of yesteryear. They span the gamut, and they span democracy through authoritarian regimes. The only difference is how it’s conveyed/portrayed to citizens, and how quickly /easily it is for any single party to gain control of a nation.

I agree that some systems are better than others, and there is still hope for better ones to come. But let’s not kid ourselves into believing China has done anything terrible that the USA has not already done in spades.

All forms of government no matter how big or small are fcorrupt. That’s how it works—they/them who bends the will of the masses wins. Either that’s done by manipulating folks into believing the next candidate will “take their pain away”, or by inflicting pain for non-compliance. Or they change the rules: voter suppression, censorship, etc and pretend they “won the election.” Or they just murder the opposition and blame it on Santa Claus.

> In short, what would this be used for?

A stepping stone to inventing new species, or augmenting humans with super-human powers… duh!

Of course each situation can be unique. I wouldn’t recommend staying at any place that overworks employees or unfairly compensates them.

I am referring to tech folks arbitrarily switching jobs JUST for a pay increase, every year or two years. What’s left behind many cases is in maintainable code where people shrug it off as “someone else’s problem.”

This might be true in tech world but in local economies does not make sense. How can folks “switch jobs” every two years when there may not be equivalent opportunities in many cases?

I’d also like to point out that while many tech folks are just as fickle with their jobs as they are with programming languages, there is a lot of benefit to holding one’s post and trying to build a better company, too.

That being said at some places stagnation can happen and then it’s obvious to switch jobs, but stability can offer many benefits over arbitrary switching for more money.

Nowadays everything is layers on top of layers. File systems from regular partitions and RAID to LVM then to ZFS/Btrfs. Virtualization of OS systems to KVM/Qemu to containers.

Operating systems function now in general is to provide a means for running arbitrary systems on top of the metal. It’s astonishing what one can do with cloud-init and a base Linux install these days. I can botch up all the layers above and quickly restart without installing anything on the base system install.

Granted, there’s always special cases but I see that “stable core” over which anything can run to be the target. Just look at the M1 chip—designed to run virtualized architectures efficiently.

So, to reiterate my point, Operating systems should target virtualization/abstraction features as efficiently as possible so it doesn’t matter which OS or workload folks run, or where it’s running (cloud, IoT, desktop, laptop, server, etc).

An additional area requiring research is security. Process obfuscation of some kind to prevent tampering etc there are still work to be done.

And then pee on the floor and do jumping jacks, run in circles, then read a magazine, then install an upside-down lectern in the living room only to realize... you forgot the television.

God save us all!

Honestly all websites should support a no-script, static version to prevent 90% of the webs BS. We used to be able to view sites with JavaScript disabled and actually things would work.

Also, instead of arbitrary cookies why not standardize authentication/authorization security mechanisms to avoid having those stupid cookie pop ups.

At this point there are common web pattern which separates the essentials from the BS—so why not get rid of the BS and keep the good stuff?

Man—all I can say is most tech companies suck these days in that way. Bought a Samsung “smart” tv and a couple months later got an update—now it’s showing McDonalds ads. Like WTF I paid $500 for a TV but that’s not good enough?

The ad industry is a cesspool these days.

I second that—memories installing gentoo on iBook G4 and getting the wireless to work felt like a nice accomplishment :)

Granted, the gentoo docs are really good so that’s where I went mostly.

The first computers filled up an entire room and look where we are now...

This is a proof of concept and surely it will be refined to make more efficient construction processes.

The web is the way for universal exposure. Regardless of speed it’s the only standardized, universal and widely used interface.

WebAssembly will be the ticket there—once it’s developed a bit more.

That being said, nothing compares to native. You could have shitty hardware by today’s standard with amazingly performant software if there weren’t so many damn layers in-between.

People are fickle with hardware though and we devs need things to slow down a bit to appreciate the nuances of each device!

I can’t argue _for_ any particular tool—just that the concept is a really good concept.

I think a lot of it comes down to folks not bothering to invest in making good tools—or developers sticking to their current workflow.

That is why I relate it to Test-Driven Development because it does require a shift in process. But the end result, I think, could be very rewarding.

Absolutely! That is similar to artists doing thumbnail sketches to figure out the composition; then once things are reasonably worked out, the chosen composition can be worked onto the final canvas; then the details follow.

That is a nice benefit of good development frameworks: how easy is it to explore new ideas? And frankly that’s why there’s an uptick in higher level languages.

Honestly, I think complex architectures are best demonstrated as diagrams—and those can be developed in an agile fashion. Stable, well-thought-out architectures can’t be slapped together without nice diagrams. There’s a ton of folks who just “start coding” to get a feature going, but when someone else takes over the project, how are they to learn the code? Diagrams are always the best way for me—and there’s limits on what doxygen says, depending on how bad the implementation is.

Main point of UML is to tackle both diagramming/architecture AND forcing basic coding to reflect the diagrams. It forces code and documentation to both reflect the architectural truth.

This doesn’t have anything to do with agile methodologies, as any task can follow agile workflow.