And they sent OSS a legal demand letter to keep paying the Iron Mountain bill for their data. If OSS actually was using IM and not just running a scam, then the data should be pretty safe, if just not accessible for a few weeks/months.
Nonetheless, <p> is automatically closed by the occurrence of another block-level element, like another <p> tag or ones like <div> or any header. <li> and <tr> have similar rules. We close them because we're not savages and want to see container tags balanced in the editor, but the html5 spec doesn't strictly require it.
I find it more accurate to refer to "A Turing Test" as opposed to "The Turing Test" for that reason. It's just one loosely-defined test; necessary but not sufficient.
The article gets things flatly wrong from its first, ah, assertion. Asserts aren't for validation: the condition is supposed to be impossible to be false, just not provable by the type system. If invalid input can come through normal operation of the program, you use a normal runtime check, not an assert.
I'm thinking of making a mobile game that's a clicker or something completely not roguelike, naming it "Roguelike Roguelike", and ensuring that the word "roguelike" appears in every sentence of the description. I'll make tens.
437 days in LEO that is, where they're still protected from like 90% of cosmic rays. Hauling enough shielding is going to take a lot of energy, and inadequate shielding is worse than none.
I remember receiving a genuine "verify your account" email from PayPal way back. The phishers didn't make it up, they were just copying actual emails PayPal sent their own users.
I'd say dump it in the ocean, but I don't guess any boat will take it. Still, sounds like they're going to make the area around the landfill stink forever.
After trying a Tailwind-adjacent library myself (UnoCSS) I came to the conclusion that it's awful, but it's the least awful among worse alternatives. Having gone through BEM, I have no desire to go back there. Layers, modules, and scoped CSS seem like they could address a lot of the pain points in semantic CSS that TW was trying to, but I've never used any of those in anger save for Vue's emulation of scoped CSS.
r/PHP literally sees multiple of these every week. To demonstrate the imagination that goes into the naming, there's another one out there called Yerd.
If you could successfully write Tetris in Malbolge, I would call that impressive indeed. Just writing Hello World was a major effort IIRC. The nature of the malbolge interpreter makes it more of a cryptography exercise than a coding one.
Framing everything as a binary win/lose outcome is pretty naïve no matter how much terminology you dress it up with. Also, complaining about downvotes is a good way to attract downvotes.
I never used to be an old.reddit die-hard, but new got so bad it chased me there to where I now use a browser extension to redirect all reddit links to old. I was convinced that the website continued to get worse so they could steer you into the app which hoovers up all your personal information. But then the app is so godawful unusable that I think we're just looking at straight-up incompetence.
So yeah, I'm in the same boat: if they drop old, they drop me.
> plus the fact that the kernel doesn't know anything about PATH (it's only your shell that does)
glibc is what deals with PATH, not the shell. On Linux, it's execvp(3) in libc which is implemented in terms of execve(2) in the kernel, but POSIX doesn't make a distinction between syscalls and library functions, so a kernel could implement either or none directly.
Lots of software licenses have “non-compete” clauses that forbid you from using it to develop a competing product. Wouldn’t surprise me if there was a compiler or two out there with that restriction, most likely niche languages.