For any point release. The platforms I work on require ten or more years of stable code bases. This absolutely rules out PHP as a development language. For a personal blog, sure, but I wouldn't trust PHP to any commercial or industrial application.

Seems like a logical next step.

You're wrong. Not only can Linux run without an MMU, MMU-less Linux runs on RISC-V. Ergo, it's likely that Doom can run on the Commodore 64.

https://hackaday.com/2022/12/0...

My god, this article is so 1811. Are all the automated milling machines going to replace human workers now? Shall we throw our shoes into them and break them?

How do I get to be a futurist? Is there some kind of application process? Because if it has good benefits, I'd like to sit around all day long and make predictions about the future, also without understanding the technologies that will constitute it.

Those of us who actually do AI stuff for a living, know far better than this.

Bingo! And the fact that you couldn't perceive that is entirely hilarious.

When you can't run the software that your job requires on them.

Okay, so what are you going to do about that paranoia? Use OpenBSD? That's too bad, because the NSA has already inserted cryptospy code into the distribution without Theo's knowledge. Oh, so you'll just compile it yourself from the sources, and read and review them all yourself? Too bad because your compiler has code in it that secretly inserts itself when it detects compilation of the OpenBSD kernel. Oh, but you're going to review all the compiler source code yourself and do a Canadian cross to build a clean compiler which you will then use to build a clean OpenBSD kernel from source? Too bad, because Bernstein has been paid gold in a secret numbered bank account in Thailand to insert a bug that will only manifest when it checks the installation of a new kernel on your machine.

Eventually, you have to put your tinfoil hat away and figure out how to get some work done on that there computer. Paranoia has a useful limit.

Yes, and people are developing games for the Sega Dreamcast as well. Existence is not the same as professional viability.

I started using OpenBSD in 1998. It was a viable, timely competitor to Linux at the time, especially for building firewalls as such.

OpenBSD is a great example of what happens when you make life too difficult for end users and administrators in the name of Security. OpenBSD has never embraced the most recent release of anything -- if it's new, by definition it's insecure and it can't be trusted. Ergo, if you have to demonstrate the latest technology in whatever you're doing, you start with a Linux distribution.

From the article: "We wanted a tool that would fit on installation media, which meant minimizing code size and external dependencies." That's the breakage mode, in a nutshell. NO ONE in the world has been clamoring for an OpenBSD signing tool that runs on a floppy. But the designers are imagining the user requirements based on their own biases. This way lies the death of any commercial or open source software product.

It's extremely common for bright young inexperienced programmers to take this attitude toward existing projects or code, so much so that I'm surprised that this is the only situation in which you've encountered this behavior.

A manager's job is to take this arrogant kid and groom him so that he can be used productively in a team environment. If he's already talking about how much your code sucks then he's got a bit to learn about presenting contrary opinions in a respectful way. All the same, you need to keep your ego in check so that his good ideas (if he has any) can be applied productively to solving the company's problems.

You start with him the way you do all new guys: assign him a small piece of the code and limit his job to refactoring or rewriting a portion of it. Make sure everything's marked in source control before you let him loose. And have him give a general presentation at the end (at the source code as well as the project level) as to why his changes have improved things. Reward him for playing nice with others and chastise him for being arrogant or a lone gun. And give him bigger jobs as he proves he can handle them.

My basic rule is to listen for as long as possible before overruling a junior programmer's opinion. Make sure that he has his chance to give his say. But after hearing it, take the counsel of your own 10 years over his if your opinions diverge. Experience does matter and there's really any substitute for it.

Instead of following the pattern on here of recommending this programming language or that, I'll suggest a different course.

First, choose a very specific field of work. Video games, insurance, pinnipeds, ASIC design... something.

Second, look at the development technologies and tools that exist in that field and are used frequently and common. Games use C++ and assembly, ASICs use Verilog, pinniped databases are written in .NET.

Third, focus on learning the technologies that are used in your particular field of interest.

This will permit you to have a marketable skill in precisely the area of programming you want to accomplish.

I am aware that many programmers consider themselves "generalists" -- and heck, I do too. But the field of programming is now sufficiently wide that ALL programmers must, to an extent, specialize. Of course you can always apply your generalist knowledge to solving one-off problems. Instead, I suggest you focus on a particular area of expertise related to your dream job.

Best of luck.

Fox News's darling for collecting poll data about political events is Rasmussen Reports. In Rasmussen Reports's methodology, they make a series of random, pre-recorded calls to landline telephones. One sensible theory says that people who still have landline phones, and who take the time to do an automated random phone poll, tend to be older and retired. These people typically vote conservatively, thus causing Rasmussen's findings to be skewed conservatively.

Likewise, any sort of "polling" of Twitter results will probably not be statistically interesting, because not everyone uses Twitter. I find it utterly unsurprising that Twitter people discuss Obama far more frequently than Romney. However I don't think that these numbers can be extrapolated to the general election in any way.

Another vote here for Google Apps and Docs.

You didn't mention other business apps like accounting and other admin functions, but I put in a vote for early virtualization of all your core apps, using VMware or Redhat or whatever your favorite virtualization platform is. When we founded our little company, we installed Quickbooks and SugarCRM and Perforce and a couple other business process apps on virtual machines, and that turned out to be a big win later on.

The thing I don't get about all these consumer-grade audio products hawking 96k sound are why engineers, who should know better, are attracted to them. It's as though we came out with a new TV that displays past the wavelengths of visible colors into the ultraviolet spectrum. Sold, presumably, with the tag line, "Our new plasma television reproduces all the colors that you CAN'T see... but BEES CAN!" Likewise, dogs in your household may appreciate an upgrade to 96k sound, but if humans cannot physiologically perceive sounds above about 22-23 kHz... then why... why...