Oh, I see. The guy was a tax cheat:
3,901 karma · joined November 24, 2010
To contact me via PinealWeb, think very hard at this spot right here. Alternatively, email me at xenophon+hackernews@irtnog.org.
The guy is President, not king. He's supposed to delegate those sorts of policy decisions to experts. Ruling by consensus, not fiat, is a _good thing_. It's like having a change advisory board or code review process vet changes before they get deployed in production.
The bit about performing for votes is a circular argument with no way to refute it. You could say the same thing about any elected official.
> "If the recommendation is approved, marijuana would no longer be listed as a dangerous substance like heroin or LSD and it would reduce or potentially eliminate criminal penalties for possession. The decision rests with the DEA, which has rarely, if ever, rejected a rescheduling recommendation from HHS."
https://www.forbes.com/sites/roberthoban/2023/10/10/schedule...
Back when they called containers "jails", I did both distroless/single-binary and full-install containers. I like the former a lot. They really make it difficult for attackers to live off the land. On the flip side, they're a huge pain in the ass to maintain, particularly if your programming language of choice doesn't make static linking easy.
Nowadays, where system admins aren't usually programmers, doing a full install of an operating system's userland into a chroot---sorry, I mean "layer"---is pretty damn handy. If you're careful about what packages you install, you can get most of the benefits of a distroless container (e.g., making LoL hard) without having to know too much about how the runtime environment works.
It's all a balance, how much time and money you waste engineering the perfect `FROM scratch` container versus getting actual work done using a "fat" image that's good enough. And I think we all know, deep down, that fat OCI images make the Docker world go 'round.
https://lispcookbook.github.io/cl-cookbook/vscode-alive.html
I'm well aware of how Elite: Dangerous's procedural generation works. Frankly, I think it's is even more impressive than NMS's, since the Stellar Forge-generated galaxy has real structure to it: the spiral arms, areas of greater and lesser density, and so on.
> they seem to have given up on [planets with atmospheres]
Odyssey planets do have atmospheres, so I'm not sure what you mean.
> Also they're moving away from VR support rather than towards like NMS... [Frontier] dropped VR.
Well, first of all, FDev didn't drop VR. It works fine in Elite: Dangerous Odyssey. The way they implemented on-foot VR as theater mode instead of attempting to hack some kind of room-scale VR system into their engine—which has great support for seated VR—seems like a reasonable compromise to me. Contrast that with how NMS implements vehicle controls in VR. They do room-scale VR, so there's no transition to seated VR when entering a vehicle, which is controlled—and I use that term loosely—by basically waving your fists around in the air to work controls you can't feel. It's pretty awful.
Second of all, VR in NMS was very badly broken as of August, the last time I tried it out. And I'm running a brand new 5700X and 4070 Ti that can play Elite: Dangerous Odyssey on VR ULTRA at 45 fps worst case.
As far as the current direction of Elite: Dangerous? Sure, there's plenty to criticize, but after over 10k hours, I'm still really enjoying it. I'm still learning new things. I'm still following the story. I'm still engaging with other players. I'm still buying ARX. With NMS, after 367 hours every system, every planet, every station, every alien has started to feel the same. I no longer enjoy it. But hell, you might really, really love NMS. If you can pick it up on sale, you should get it.
At the galactic level, well, first, I never know where I am or what direction I'm going. In NMS, you don't see some oddly bright splotch of light slowly resolve into huge nebula as you slowly jump toward it, like you might in Elite. NMS doesn't seem to render much of the surrounding galaxy when it generates the skybox. There's definitely no sense of galactic orientation because there isn't anything like the Magellanic Clouds or distant galaxies off in the far distance. Your only views of the galaxy are either of the immediate vicinity or a tiny thumbnail.
But hey, without getting too far into spoilers, the whole "obviously procedurally generated" thing is part of the NMS universe's conceit, right? And out of universe, it's clear that Hello Games explicitly set out to *not* create a sim like KSP or Elite: Dangerous but rather something with a unique story and a different player experience entirely. I respect that. The game's a lot of fun, and the story it tells is deeply engaging, if that's what you want.
It's like Elite: Dangerous or Minecraft. There are all kinds of loading screens, but they're all pretty cleverly hidden. On planetary surfaces, you can see chunks load as you drive or fly towards surface features. Every teleport is a loading screen. So is entering and exiting a vehicle, landings and takeoffs, entering/dropping from NMS's equivalent of supercruise, or warping to other systems.
My one big gameplay complaint is how lost and directionless I feel in NMS compared to Elite: Dangerous. Like, in Elite I can see a nebula or some other galactic destination and plot a course toward it, settle in and explore an area, and so on. But I never quite feel like I can know where I am or see—at the galactic level—where I'm going. I'm not a huge fan of the spaceflight mechanics, either. And VR in NMS seems completely broken on my brand new gaming machine, which ultimately got me to uninstall it.
I feel like I got a lot of entertainment out of my $6 NMS purchase, so none of these criticisms are to say the game is bad. If you've never played it and think you might enjoy a hybrid of Minecraft and Elite: Dangerous, it's the game for you! And I'm very glad to hear the game and the player base are still lively. Great community there, especially with player groups like that taxi service, or various colonies, or resources like the Glyph Exchange.
P.S. I have to second the "simultaneously too small and too big" feeling of NMS. Space in both KSP and Elite feels scaled well. Then again, I came to NMS late, so maybe how KSP and Elite do things only feels natural because I played those first.
Then you don't know about Palladium, a/k/a the Next Generation Secure Computing Base, which Microsoft started developing in 1997. It's explicit goal was digital restrictions management. They co-founded the TCPA in 1999 to develop the TPM hardware spec.
SQLite, for all it's features, has some pretty significant limits. In my case, I needed better date/time and decimal type handling than what's on offer in SQLite. I still test my code against SQLite because that is a useful way to lint my data model—plus it's nice for small-scale proof-of-concept deployments—but I expect deployers to use PostgreSQL or MariaDB in production.
Edit: I've had a chance to read the article. The comment about "zero latency" is wrong because it ignores disk I/O. And yes, I know SSDs are super fast. Still not zero. The bit about Docker Compose rings hollow. It sounds like they need to learn how to use multiple Compose files, e.g., https://mindbyte.nl/2018/04/04/overwrite-ports-in-docker-com.... As for development and testing, mock database setup should be handled by your unit test framework. I'm familiar with pytest, which makes testing the same model or ETL across multiple database fixtures very, very easy. SQLite has nothing to do with that.
You aren't using Wikipedia as a source but as a partial and severely biased index of the reference material. You must still be very skeptical because you have no idea what led a page's editors to include or exclude a particular reference. Frankly, you'd be better off contacting the reference desk of your local library. That's what it's there for.
The ChatGPT conversation has zero value as a source in the abstract.
> It feels just somewhat like when I was told not to use wikipedia in my early school days.
Do you understand why you should not cite Wikipedia?
https://svn.so-much-stuff.com/svn/trunk/cvs/trunk/games.d/vt...
It's really old and I never got it working on more modern operating systems. One of these days...
Nothing's stopping you from doing it that way, but since Steele and Moon started writing EMACS in 1976 on the PDP-6 and the PDP-10 and probably used VT52 terminals to access those systems, you're probably expected to have a control key on the home row to the left of the caps lock. The VT52 does not have a control key on the right side of the keyboard. I've found that Emacs's ergonomics are greatly improved by swapping the caps lock and left control keys on modern, IBM Model M-inspired keyboard layouts.
YOU, a relatively wealthy programmer/middle manager living in a first-world country, have access to such a device.
Ever think about who you're disenfranchising with tech like this? Or to whom you're ceding socioeconomic power and political influence?
Whether attending a conference for a hobby counts as a vacation trip or a business trip would be a question for the destination country's consular affairs office.
In the U.S.A., lying on a government form is illegal, https://www.law.cornell.edu/uscode/text/18/1001. I can't imagine other countries treating that differently.
If you're new to Homebrew, make sure to set the environment variable HOMEBREW_NO_ANALYTICS to 1 before downloading and installing it. Otherwise, it defaults to spying on you.
Real Programmers stored their source code on magnetic tapes, that is if they weren't using punch cards or paper tapes. RCS, the first open source version control system, predates PKZIP by a good five years, and SCCS, the first version control system, is only a year younger than the first commercially available floppy disk drive.
But never mind that. Git was at most an incremental improvement over its direct predecessor, BitKeeper, or the other popular version control systems at the time, like Subversion. Git wasn't even unique. The open source DVCSes Arch, darcs, and Monotone all predate Git, and Mercurial was started just a few days after Git. Our hacker parents and grandparents might be old, but they aren't _savages_. ;)