Edit: I was a bit quick to post. The article I linked says Arthur David Olson (mentioned in sibling comment) started the TZ database, with Paul Eggert extending it and maintaining it later. The 2011 lawsuit is also mentioned in the Wikipedia page I just linked.
The phrase "disqualifying crimes" did a lot of heavy lifting here. While some obvious ones will get you disqualified, e.g., murder, there are a number of less obvious ones, including minor drug offences and resisting arrest.
Your comment led me down a bit of a rabbit hole and I found this on Wikipedia:
When writing in languages such as Danish and Norwegian, where the empty set character may be confused with the alphabetic letter Ø (as when using the symbol in linguistics), the Unicode character U+29B0 ⦰ REVERSED EMPTY SET may be used instead.
It also mentions what you are alluding to:
In the past, "0" (the numeral zero) was occasionally used as a symbol for the empty set, but this is now considered to be an improper use of notation.
And, as a programmer, don't get me started on nulls...or undefined...or truthyness.
As a Norwegian, I find it annoying that they "stole" Ø for that purpose. I put a backslash through my zeros instead, so it looks different. I usually pick a coding font with dotted zeros for the same reason.
Yep lol. I live in a small rural Ohio town. When I first heard it, it was from a friend's wife and even he had to look it up. She grew up on a small farm nearby.
Programming is mostly understanding something abstract in your mind not rote memorization.
Even for a very simple program, focus on understanding what it does and how it does it, and why, step by step. Write things down when you learn something new.
Reading and understanding code, especially good code, will make you a good programmer. Just writing a ton of shit code will not. Trust me, I've done this for 3 decades and learn something new almost every day from reading other people's code.
So, focus on understanding what it does, and you will be able to modify and build programs from scratch soon.
Just wanted to add some context to the quoted part of your comment:
However since few new users had download capabilities (because they never used command line FTP before)
A lot of people didn't know how to download things, sure, but another barrier was most people were on dial-up. It would take a long time, sometimes on expensive calls, to download software. And getting disconnected often meant starting over.
Even if you didn't mind downloading, it was unusual enough at the time that a lot of people probably just felt safer buying the disk from a retail store. It's tangible. So people would get software either off the shelf at the store, or free as part of another purchase.
For example, when I worked for ISPs in the late 90s, we gave every customer a floppy or CD with a dialer and a browser. One popular one among ISPs was the Netscape dialer + browser bundle that we could customize and lock down the settings we wanted, like DNS, proxy, POP phone numbers. I remember we charged $19.95/mo for dial-up in 1998, but at least you got free email and a homepage so you could put up HTML pages with animated GIFs!
Early on there were many different browsers, too. Some based on Mosaic, some independent (e.g. Opera). Netscape eventually became the most common one. I think IE may have been based on Spyglass Mosaic. Microsoft definitively felt threatened by the idea that the web and Java (applets!) could make their entire golden goose, Windows, obsolete. Write Once Run Anywhere was an existential threat to them. So, eventually they ripped out the Microsoft Network (forerunner to MSN) and put Internet on Windows instead. It took them a while, though. And that was only in Windows 95. We were using the WWW before that. (Trumpet Winsock anyone?)
Sorry for going on an old-man rant. This triggered some really crusty memories.
I remember hearing about this in reports from major hurricanes in the South. Sounds pretty horrifying to be stranded on a roof or floating around on your own makeshift raft and then happening upon one of these ant rafts of doom.
Edit: thanks for the nightmares everyone. That'll teach me to read Lemmy right before bedtime.
On your first question: the current law is that DST is optional, but if a state opts out, they have to be on standard time. The new bill allows them to stay on DST permanently and removes the ability for states to opt-out unless they are already on year-round standard time. So, if this passes, every state in the union will be on either standard time or DST, depending on their status before, with no option to either go back to standard time nor to go back to changing twice a year.
Yeah I'm not holding my breath. It will be around for a long time.
A couple of things I could see changing that would be a) Microsoft in financial trouble, b) AI both making it harder to keep up with security bugs, and making it easier to migrate away from legacy systems.
The chances of .net framework being among the first to go is slim though.
Good call. I'm getting mired in the k8s side right now and we have dozens of small web apps that need upgraded and a couple beefier framework apps that need essentially rewritten. Unfortunately I can't escape lol.
We an ecosystem I overall like .net core and I agree it will stick around. I just can't wait to get off IIS and into Linux even if that means complicating things with kubernetes.
Modern. Net is portable and fast, yes. But .NET framework is (mostly) not portable and it's tied to the version of Windows is on. We'll see when Microsoft decides to EOL it but so far it has not been announced. It's not getting more than security updates now, as far as I know.
We're converting everything we can (mostly web apps) to modern .Net (formerly core) so it can run on Linux. I may be stuck on Windows at work for the office apps, but my code runs on Linux.
Agreed. I don't think I explained myself clearly enough: I want them to have a presence online. Among the reasons being exactly what you're pointing out. However, I think at least for smaller cities with very little staff, it's not realistic to ask them to literally self-host it (as in having a server on-prem running it). I would be fine with them outsourcing it or cloud-hosting it under their own domain.
A potential solution for the small ones could be something like a state-level hosted service where municipalities can sign up and get their own accounts, for example. That would work even for something like Rittman, Ohio pop. 6,131.
You're probably thinking of Paul Eggert.
Edit: I was a bit quick to post. The article I linked says Arthur David Olson (mentioned in sibling comment) started the TZ database, with Paul Eggert extending it and maintaining it later. The 2011 lawsuit is also mentioned in the Wikipedia page I just linked.