Been looking into this for a while myself, very cool. It seems .nl has a lot of resources and support for this sort of thing. Any similar resources like coloclue in the San Francisco Bay Area? It seems confusing to find just a couple of U of rack space in SF that you could peer in and out of?
I'm actually not sure the Northridge earthquake was cited in the Richter scale, most references I see have it as about a 6.7, which based on the USGS catalog, was it's moment magnitude 6.7 Mw
Yes, this. Which the counter point is either, Don't align things, or use tabs for indentation, and spaces for alignment.
And maybe you can enforce no alignment, but that's a hard fight to win.
And as far as tabs for indentation and spaces for alignment, I've found no practical way to enforce this via tooling/linting. And a rule without enforcement becomes inconsistent, which is how we get files full of mixtures of spaces and tabs, which is how people get frustrated with tabs, and we decide to throw it all out.
These regexes don't solve what I think is one of the major common problems/complaints though: using extra tabs past the logical indent point as a shortcut to avoid typing so many spaces for alignment purposes.
To take this example from a sibling post:
if (foo) {
» frobnicate(bar,
» ...........baz);
}
Many people will wind up doing this:
if (foo) {
» frobnicate(bar,
» » » ...baz);
}
And then your alignment is all messed up if you have a different tabs setting.
Checking for that requires something more like a linter with a detailed understanding of the syntax parse tree.
For example, I considered writing a small Awk program to check C code in response to another poster’s complaint about lack of tooling, but then quickly came to the conclusion that, with C’s insistence that (say) /??/<newline>* is a valid comment starter, getting this exactly correct probably does need an actual lexer that would go character by character. That sounded like it wouldn’t fit in an HN comment, so I stopped there.
(That said, that’s as far as you’d need to go in the majority of cases. A dishonorable mention is warranted for languages that use the same character as an operator and a paired delimiter simultaneously, that is C++, Java, C#, TypeScript, and Rust with their abuse of the less-than and greater-than symbols, because that would in fact require a parser. In C++ especially, you’ll need full semantic analysis with template expansion, name resolution, and consteval evaluation. Because C++.)
Yet you probably don’t actually need to be that accurate, do you? The majority of syntax highlighters aren’t, and they are still useful. You can usually afford to say that code that perverse deserves to lose, and in return I expect you should be able to gain a fair amount of language independence, which could be worth the tradeoff.
So instead of checking if things are aligned with what they should be, you would just check they are aligned with something, like a left word boundary preceded by a delimiter, and so on. I can already see unpleasant corner cases after thinking about it for a few minutes, but it doesn’t look hellish yet, it looks something like you could experiment with over a weekend to see if it was viable.
It would be crazy that spaces would have "won" because of the silly idiosyncratic alignment that some people seem to like and then teach to others for many decades.
> Legally perilous maybe, although my non-lawyer brain sees that as fair use, especially if the emulator doesn't let you play the full game. Idk, but it'd be a unique thing on the internet.
IANAL, but I think what a lot of people don't understand is that "fair-use" is a defense. Which basically means you have to be prepared to argue in in court. A lot of potential fair-use is quashed before it gets to that point.
It's also a balancing test, which means that it's very fact/context dependent, and subjective, which results in for a lot of cases, you really won't know until you actually get to court.
This is incredibly relevant to projects in this space, and we continue to hold discussions about what is and isn't tolerated in our community, and what features we should avoid building, in order to protect ourselves from legal attacks. One thing you'll never see integrated into the RomM is a way to pull/download ROMs from cloud services or website; you'll always need to provide the games to RomM directly, after sourcing them legally of course.
Honestly, it's probably simpler than this, and the root of the problem often comes down to the Cloud Providers to begin with.
It's astounding the frequency I get an email from some cloud provider, or mobile app store that says something to the effect of:
"(Version X) of Dependency Y that we convinced you to use 5+ years ago is getting deprecated on August 1st, if you don't upgrade to Version X+5 you're service will go offline"
And we're stuck looking at the minimal amount of players running of that platform, and the hard choice of do we move precious human resources off of some in-progress game, that's already running late to learn a system that they never worked on, because the original people are long gone?
So, that's often why our network services, and mobile versions of our games are being taken offline while the single binary we shipped to one of the serious console vendors 10-20 years ago is still running, and now running on consoles 2 generations newer.
So, yeah, it'd be great if we could ship a package for Amazon to host perpetually, but first you could just get Amazon to care enough to ship a stable platform to build upon that wouldn't get depreciated.
But then, having also lived it, upgrading to newer versions of PHP and it's required modules is also not trivial.
And it's often not just your language, the cloud vendors have a lot of incentives to get you to use their hosted Postgres, or AuroraDB, or GameLift. Or even something as simple as we built all of our deployment scripts/images for our PHP system on Amazon Linux X, and now for reason Y, only Amazon Linux X+2 is supported.
>B. Google lacking the same persistence of Amazon (Consider all the products that are killed)
Yah, like the Stadia, Google's streaming gaming console thing. They even had a first party game development division for it. So exactly what OP was wondering about.
Ugh, on both mobile platforms, we have/had multiple popular games that their updates keep breaking, and they keep deprecating SDKs for. And each game is at on a different engine revision so we can't combone the work. We'd really like to keep these games up for for our mobile players, but we can't justify the cost, we make some money on these platforms, but nothing that justifies the immense cost.
Meanwhile, our console/steam/gog builds have seen an update or so at our discretion, and have just continued to run happily, and make more money.
Honestly it's hard to justify the maintenance effort to even consider porting out next games to mobile.
But really the people who are hurt are our players that already bought our game, but when the upgrade phones or OSes they no longer have an option to play unless they want to transfer their licenses to PC.
I'm actually really curious what the experience is like having not more than 10 tabs at a time, like what thing causes you to close a tab? 10 seems sort of wild to me, it's enough that you are clearly not just monotasking, somehow bounded. Probably in contrast, if you could imagine just forgetting to do that whole closing tabs thing, eventually you have hundreds or thousands of tabs.
Some context, for starters, I have about 10 tabs pinned, discord, 3 slack instances, my fastmail, my gmail, my work mail, spotify, my task list.
Then, there is the things I left open because I am going to read it, a stack of documentation I'm working on. A few random products I'm researching as procrastination. Any search I'm on, and a tree of tabs from different results that I'm working through.
There are the various layers of those things for the things I was working on 30 minutes or a day ago, that I haven't worked back to yet.
And most importantly, there are all the tabs that used to fall in the prior categories, that I just forgot to close, or haven't gotten around to closing yet.
