Real engineers are required to follow a code of ethics. Good thing software engineers aren't!
3,988 karma · joined October 3, 2019
That said, I wouldn't use a registrar that didn't have good reviews, and I'd look at security policy, privacy policy, renew price, features list, and support options. Sometimes it's worth paying more.
After you have the domain, if it's important to you, try to get support to change it for you or recover your account without a valid email address. You'd be amazed how easy it is to compromise many registrars through support.
And set up auto renew... Once it's gone, you'll regret it.
Even if you can't sustain it forever, you're getting fitter than if you weren't doing anything, so your life expectancy is still getting longer.
Parking lots are parking lots because they require low CapEx, almost no OpEx. You buy some abandoned land, raze it, asphalt it, charge $30 a day per space (at let's say 75 spaces), tow the rest (at the driver's expense). You're pulling in a little under $67k/month. Wait for a commercial developer to come buy and take it off your hands for 3x its value.
You know how much it costs to dig up the ground, install power lines, a box, then bury footings, bolt in legs, install panels, etc, 9+ feet high? For a whole parking lot? $300k-500k, minimum (that's how much it costs just to install a small fleet of EV chargers btw, that's not doing major construction over an area the size of half a football field).
How much you gonna make off these panels? A 200kW panel array generates about 480MWh/yr, which at 1MW/$40 comes out to about $19,200/year in SREC credits. PA energy price is $0.18/KWh, so 480MW is $24/hr. But you're making 80% efficiency and it's not sunny all day all year, so at even 50% usage, that's $24,960/year. Almost a third of what the parking lot makes a month. Before we talk paying back installation costs, assuming your net metering deal is perfect.
It would be cheaper to build a multi-story garage, where you'd make WAY more money.
In cities outside of Baltimore, where there aren't 20,000 abandoned buildings (when last I lived there), where there's a public housing shortage and a rising cost of living, they need affordable homes, not trees. I love trees but they're better for cities that don't have housing shortages, yet have the money to pay for trees.
Baltimore (and Philly, similar in some respects) has large concrete and brick deserts. But they also have large and small parks with lots of trees. That's where you get mugged after dusk (and sometimes during the day). You don't walk through Patterson Park at night.
IMO it's a privileged thing to think of first. Certain websites that cater to this kind of post don't seem to discuss civic issues from the perspective of the people who need the most help. It's more a certain kind of person who's more interested in a closer walk to the Starbucks and Trader Joe's.
The point is that a message queue is just a concept. It can exist in many forms for many different use cases. You evaluate the type of queue and implement something that provides for its requirements. HTTP does that inherently for certain message queue types, and for others it requires more code.
Another example is the perennial meme of "PostgreSQL queue". A database isn't a message queue, it's a database! Yet people throw some crap into the DB and call it a queue. Because the application doesn't care how you implement the logical concept. HTTP, RDBMS, MQTT broker, whatever.
(Japanese isn't so radically different from English, it mostly just has more words for more contexts. In many ways it's simpler than English. It would be harder to go from Java to Haskell, with their many different language paradigms)
That said, if you want a customizeable FOSS message queue stack, use NATS. I'm not aware of a better, more complete solution designed for custom integration.
You're better off hiring experienced people who are highly productive. If they're highly productive with one stack, it makes no sense to change their stack so they're no longer productive, or hiring people who aren't familiar with it and waiting for them to become productive.
There's nothing wrong with using old, well established things. They're quite often better than new things. As long as they're still supported, just use whatever builds a working product. It's the end product that matters.
That's not the big concern though. The big concern is whether vendor integration and certification becomes a stumbling block. You can hire any monkey to write good-enough code, but that doesn't give you millions in return. Partnerships with vendors and compliance certifications can give you hundreds of millions. The harder that is, the farther the money is. A totally custom, foreign stack can make it harder, or not; it depends how they allocate their human capital and business strategy, whether they can convince vendors to partner, and clients to buy in. Anything very different is a risk that's hard to ignore.
IllumOS is the OS/360 to Oxide's System/360. (It won't get that popular but it's a fair enough comparison for illustrative purposes)
Actual probability you will get NHL from roundup if the figures are accurate (again, limited study results, no causation found), in the worst case, goes from 2% chance to 2.8% chance.
Amazingly, none of this considers the additives to roundup that aren't glyphosate, which everyone agrees are much more likely to hurt you. The case seems to hinge on the least harmful part of Roundup.
This whole case is a great example of a lack of scientific literacy and a whole lot of fear, combined with a dislike for large corporations, resulting in a whole lot of disinformation. Roundup might be bad for you, but we still don't actually know, because we have no causative proof.
Imagine a tattoo artist creating a tattoo, and then another artist makes a bundle by stealing the first artist's design. That's what copyright is there to protect.
Just like she deserves to make money by creating art, so does the photographer. Can't have it both ways.