skysight-inc/HackerNews huggingface dataset:
Even more whimsical option: Evangelion is set in 2015, which means if we were following their projected technology timeline, we could just unload the ship by Eva. Probably unit 0, because Rei tends to get the crappy jobs. Not Asuka, she'd turn it into a contest of who could sink the most tugboats by throwing containers at them or something like that.

The Evas can be airlifted anywhere in the world, but IIRC they have about five minutes of battery power. So, the biggest logistical problem would be getting suitable power on site. What are the voltage/current/frequency requirements of an Eva charger? How many months/years would it take to charge an Eva with a J1772 port or whatever they use in that part of the world? Looks like the nearest Tesla superchargers are in Israel and Jordan, which is too far even if they were compatible. Maybe NERV has a mobile generator?

The Jet Alone folks could put in a competing bid, but their robot would just get sabotaged again.
Armstrong isn't even talking about functional programming, he's obviously talking about messaging and actor systems.
This explains how "-i inplace" works: https://www.gnu.org/software/gawk/manual/html_node/Extension...
It has been growing nicely for a few years.

The pandemic helped retro, IMHO.

Whatever the cause, I love to see all the stuff people are doing, and the whole scene reminds me how far we have come.

[Looks over at 1Mhz Apple //e, thinking about some fixed point code to drop into that retrogame project...]

What I did was buy some goodies. 16Mhz CPU card, CFFA for disk storage. Floppies are getting super long in the tooth.

Now the machine can be really quick! Lots of fun possible.
as a sysadmin, i hate this... but I'm also thinking of using it.....
Assuming you narrowly dam up the canal near the ship to contain the brine, no I don't think so. Seawater is 3% saline and saturated brine is 26% saline, so you'd probably have sufficient mixing within the canal itself once you open the dams. The canal is 120 miles long and I can't imagine you'd dam up more than a third of a mile at maximum. But it would take a whole hell of a lot of salt.
Hyper-V can do that too, and so can you under Linux. It's called thinly-allocated disks, sparse files, or the dm-thin device mapper target. Professional SANs also allow you to overallocate the total size of the iSCSI volumes offered.

Yes, I've seen that time bomb go off on multiple occasions. Never on my watch though.
I happen to run a couple of small servers myself and here's a better version of this approach. Create a cron job that will run a simple self-testing script once every few hours. My self-test does this:

1. Checks that all domains can be accessed via HTTP and HTTPS. If not, DNS might have died.

2. Checks that a few known CMS-generated pages contain some phrases they should contain. If not, SQL might have died.

3. Checks that the HTTPS certificate has enough runway left. If not, certbot might have died.

4. Sends a basic email message from my domain to a gmail account. Receives it via IMAP and sends a reply. Then, verifies the reply. This catches a whole bunch of mail-related issues.

5. Checks the free RAM and disk space. Updates an internal "dashboard" page and sends me an email if they are off.

It only took a couple of hours to hack this together and I must say, I get a much better night time sleep ever since.
A bottle of wine was blasted into space. Here's what it tastes like now
I'd suggest that OOP has it's niche. Primarily it's a methodology for limiting the effects of changing state while keeping the codebase performant. Removing state where possible is obviously going to be the safer course of action, but immutable data structures are not as efficient as their mutable cousins. This may not matter for much software, but where it does, OOP isn't the worst solution when used selectively.

The problem with OOP in 2021 is that it tends to be the default, when arguably starting from safety and working back toward performance would be a better approach.
It was about a megabyte per cassette tape, depending on the encoding, right (counting both sides)? Doable, with lots of tape swapping, I guess :)

Though probably a shorter version would be nicer

[edit]
Forget that, from the Reddit link:
“We end up reading data at about 533KB/sec, and are I/O bound.”
If we're going unrealistic, there are even better plans:

https://www.youtube.com/watch?v=5guMumPFBag&t=123s
Would your "free market" also mean that the people living in the suburbs pay the true cost of living in suburbs? Including higher taxes to offset the higher infrastructure costs and the higher impact on the environment?
A vented closet would be in order. Pretty sure management and customers don’t want packages sharing the same airspace as a toilet.
It reminds me of the last Star Trek Voyager when the Borg Queen had to cut off the Borg network to slow down / prevent the spread of the virus from Captain Janeway.
Better than the coronavirus takes I've seen from software devs...
That beast is really outstanding and would probably be able to do the job in reasonable time. This machine is so insanely large, it would fit into any sci-fi movie. The craziest thing is, some years back it was driven over a distance of 22 kilometers cross country to a different site, which was just mindblowing.
Prior to the pandemic, if you and your spouse both had jobs where you worked in company offices, then paying extra for a house that would support home offices for both of you is a huge expense. If you think every couple should do so just because they might both need to work from home some day, then you seriously overestimate how much extra money most families have available. Or underestimate how much money those extra rooms add to the cost of a house.
> Someone else perhaps had a similar idea, so were writing libfossil; however, they seem to consider the protocol implementation a lower priority,

That's me (https://fossil.wanderinghorse.net/r/libfossil). The protocol is irrelevant to the implementation of the underlying core algorithms and data format. The sync protocol is a completely separate layer which can be reimplemented any number of ways without affecting the underlying data model. Without the core data model and algos implemented, the sync protocol is useless because it has nothing to sync.

Ergo: first implement the data model, then the sync.

> (however, they consider it important to use the same database schema, while I don't, and can freely rewrite it)

That's a really interesting topic, actually. The core data model is 100% independent of any given schema (or storage model, for that matter), so anyone implementing a compatible (at the data model level) tool is free to use whatever storage or schema they want. The fact is, though, that libfossil could never have gotten as far as it has without re-using much of what Richard has already designed, and that includes the schema and core SCM-relevant algorithms. As a long-time fossil contributor, it's important to me that the libfossil tools be as compatible as feasible with fossil, and that means using the same schema (for better or worse).

That said: i would very much like to see the core data model implemented on top of another schema, just to see it done. Alas, i don't have the energy to create, from scratch, such a beast, nor to maintain it, so my path is one of lower resistance: re-use what's already been designed and which works well within the fossil project. i'd love to see what you have when you're ready to post it, though. (i recall you(?) posting about this in the fossil forum before - feel free to announce your project there when you're ready.)

> As it turns out, both of us had independently used the term "deck" or Fossil structural artifacts.

What else would one call a "container of cards"? :)
The best comedy approach is to hire Planet Express to fly in a giant can of WD-40. That stuff will get anything unstuck.
Yes, it is very remarkable indeed. Some of these advances are really amazing and I am hopeful it will improve further.

The reality now is that e.g. Waze is not even able to recognize a broken, curvy road that is a bit shorter, but not really worth it, especially not at night and rain. It is not able to recognize a pattern of choosing the other road either. It can also not read house numbers in Czech properly, so it says not "house Nr. 42" or "house 42" but "house 42nd". Also, Google, Waze whatever often don't understand my and others English when giving commands and I was never told that people couldn't understand me. I do have an accent but I speak quite clearly as a singer.

There are many, many areas, where the computer doesn't support the user at all not speaking of adapting to the needs of the user automatically. People are instead constantly bothered by unimportant stuff, SPAM and settings where sane defaults would prevent 99,9% of the issues.

I guess, it is a matter of priority, focus and business model. If bothering people "engagement" is your business model you will not be motivated to "get out of the way". This is the same with ads. I don't mind good ads in a reasonable amount, good ads can be funny, interesting, educating. Nobody really thought about how to do really good ads on the web - it is mostly some trash I am not interested in in the slightest. Therefore people are using ad blockers, because too much is too much. Where is the UX there?
I'll be the next to confirm this, and on multiple machines.

Maybe 1 in 5 that I try will be a reasonable startup time.
Being able to search apps by really basic properties is an embarrassing missing feature of google play store.
But what about growth and engagement? I wouldn't be surprised if some idiot's performance metrics are tied to how many people "engage" with the calculator.
> That could destroy the boat, but... so what?

Because then you'd still have to remove everything, but now you don't have one big, controllable system, but you have lots of pieces that will move in unpredictable ways.

The canal is shallow and narrow, and gravity isn't working in your favor here. A ship has a natural tendency to float (even if it currently isn't). Pieces of debris don't. You will have to remove all pieces that break off, one-by-one.
Amazon really thought denying that one would go down well???
Now that is an interesting idea.
How to Install HestiaCP and Create a New Website on Ubuntu 20.04
You’re right that Python only has function scope, not quite lexical scope. But

perl -e '
sub foo { $x = 42 }
foo;
print "\$x is $x\n";
'

quietly creates a global variable. You have to ask for lexical scope, and you have to ask for strict mode to get that error (requiring 5.11 or better does that, but merely having 5.11 does not). Backward compatibility justifies this but devs need to beware this is how the language used to be.
Spoilers?
If Apple cared what ARM thought, they would have finished implementing the spec. AArch64 is as much Apple's as it is ARM's and I doubt they're scared. They have a do wtf you want license and ultimately don't really care if the rest of ARM withers and dies.
> That's just an argument for better testing. That's not implementation verification.

No, I'm not talking about testing, I'm talking about really basic formal verification:

forall (x: Certificate), verify_certificate(x, flags = 0) == invalid ==> verify_certificate(x, flags = STRICT) == invalid

This is trivial to specify and almost as trivial to prove to be correct for all inputs. Testing can't do that, no matter how good your testing.

> Only if you thought to write that test to begin with. Writing a test for everything is... not really possible.

I agree, but I'm not talking about testing. I'm talking about formal verification.

> It's not. The reason the strictness flag was added was that OpenSSL was historically less strict than the spec demanded. It turns out that when you're dealing with more than 30 years of history, you get kinks in the works. It wouldn't be different for whatever thing replaces PKIX.

That's totally fine and wouldn't affect the verification of that function at all. This is a very simple property to verify and it would avoid this bug and all similar bugs in that function (even if that function calls other functions, no matter how large or complex they are).

Other functions also have such easy to verify properties, this is not hard at all to come up with (although sure, some more difficult properties might be harder to verify).

> You must be very popular at parties.

I didn't want to be dismissive of OpenSSL devs or other devs in general, I just find it frustrating that there are so many myths surrounding this topic, and a lot less education, interest and investment than I think there should be, nowadays.
> "Dorsey is seen as quite evil for those who know him in my circles, rather like a Taliban in his last congressional hearing"

Do you mean people who know of him, not know him personally? That's the only way that makes sense because if they knew him personally I don't see what his looks in the hearing have anything to do with it.

Personally I'm surprised Dorsey isn't received better. He's clearly the most social mission oriented. Gave away 28% of his Square equity, Twitter is barely profitable, and his SF lifestyle is fairly modest in comparison to these other super-CEO's. He just doesn't strike me as one who cares much about personal wealth. But I guess the distaste comes from his tweeting for leftist causes.
It kinda does sound like fun, in a world where I didn't already have several large projects in the works I would be tempted to fool around with some Neo-Geo homebrew now!
I think the major concern is the motivation behind the change. From the report HR's response to pushback on this change was basically "we don't care what this breaks deal with it, we are not reverting, implement a workaroud, end of discussion". This seems highly unusual for what seems essentially to be a technical change. For starters, why is HR involved at all in this change?
Are dredges normally expected to access underneath a ship? I thought under the typical use cases they have a clear work area.
This is the comment that proves the rule!

This is such a good idea that it actually exists and works.

Look up water injection dredging.
Archiving is likely solving the wrong problem, for legal reasons they don’t want those old emails hanging around.
You are right, I changed it to malloc.

This 'long way' thing is definitly not super useful..
One topic is that there is an entire domain of software that never needs to deal with decoding strings and manipulating them. That is, it can deal only with strings in their entirety, and only care about the size of encoded bytes. One such piece of software is the Zig compiler itself. So the question is, assuming we have a package manager that works well, is it worth it for the standard library to take on a large, volatile dependency of the entire Unicode database, for the sole purpose of ensuring the ecosystem has a canonical string handling library? I don't think the answer is obviously "yes".
Thats the point im making. It took leveraging search to offer premium real estate for AMP pages to force adoption. It was a compelling value prop for top publishers. Enough to boil the ocean. However, simply asking the ecosystem to build faster pages.. isn’t going to work.
Of course it will affect unionization, that's the #1 sought effect - to silo unionization efforts into individual locations and atomize them.

As for companies becoming "overly political", mega corporations will ALWAYS get involved in politics. The question is whether it's public or in the shadows. The other side is corporations trying to PR their way out of abuses so they can keep a good image and lessen progressive opposition.
After how many years is it not a spoiler?
That is the least spoilery thing that can be said about the very complex two-parter finale from 2001.
Maybe people just find it to be an interesting problem and are having fun thinking out loud about it.
It's not the state that's the problem, it's the state being bundled with the code that operates on the state.
I think developers do. Very much so. if they didn't every developer on this thread and this site would have been publishing their best work as open source. We know that is not the case.
The people that write open source code are either academics, working on the project while being funded by their employers, have a business around it, trying to build up some resume credit or building or aspiring to build a business around their projects.
There is of course the "hack project" or learning in progress project that one could publish, depending on one's reputation and standards
People who are full time working professionals and have additional personal responsibilities could not be publishing and maintaining high quality open source. This is a shame, because those people would probably produce very high quality open source code if only they could afford to pay the bills in the meantime.
What I am wondering though is whether the funding through something like this Open Collective initiative could ever match market rate a professional would command in a developed economy.
That's what college textbook OOP taught us. It only took me a couple decades to figure out that college textbook OOP taught us wrong. If all you're doing is hiding state, it's like sweeping dirt under the carpet - you're skimping on your work now, in a way that will only create more work later.

Good object oriented design goes much, much further. To quote Alan Kay, "Doing encapsulation right is a commitment not just to abstraction of state, but to eliminate state oriented metaphors from programming." (emphasis mine)
https://en.wikipedia.org/wiki/Tyranny_of_the_majority

Cool
wow a typescript lesson, because no one's ever heard of this

> Heck it could just be integers and be even simpler.

statement that has zero point, why make them?

> As do the reducers

like this? A | B | C => B | C | D

does that look like a state machine? Because state machine is this A => B & B => C & C => D
I agree with Martin Odersky that functional programming within an OO approach to code organisation is the most sensible trade off between maintainability and bug reduction.
It makes you wonder if anyone has an old aircraft carrier they'd be willing to use as a battering ram. Try to hit it towards the bow to dislodge it.
Can you ask him what he thinks about using cofferdams for raising the water level ( instead of lowering it).

I'm actually curious in hearing potential problems or ( if it would be plausible) a raw estimation of duration ( since you mentioned 20 weeks, that's a huge timeline).

Edit: I don't know anything about this subject. So it's interesting to learn/ask some stuff I wouldn't encounter otherwise.
There are helicopters that I think can be used for (un)loading containers:

https://en.wikipedia.org/wiki/Sikorsky_S-64_Skycrane
Transporting heavy equipment is really difficult and slow.

Suppose we want the very best. Let's put Bagger 293 by the stern and Bagger 288 by the bow. Come up with a plan to transport those from Germany to Egypt in a few days.

For reference:

https://en.wikipedia.org/wiki/Bagger_288
https://en.wikipedia.org/wiki/Bagger_293
http://www.swapmeetdave.com/Humor/Workshop/Trencher.htm
http://www.wisoveg.de/rheinbraun/rb-bg-17022001lnk.html

Don't forget to supply 16.56 megawatts of power for each of them.
The conclusions are similar to what I've seen in this talk by Kevlin Hennley: https://www.youtube.com/watch?v=ZsHMHukIlJY

And I think they are pretty reasonable.

I've used camelCase a lot but I am about to switch to the good old underscore_style as it really might be easier to read.

And there is no doubt in my mind that alignment, spacing and structure is almost as important as good naming.

And of course, Allman style braces.
I was thinking the same. Get lots of pumps in, drill into the sand bar and pump water to fluidize it. But it's probably still a scale thing, all the proportions involved in this problem are ludicrous.
There was interest from several large companies in reserving capacity in several different locations while I was there. So it's definitely happening on some level.

That said, that's kind of "boring edge", companies that just want one closer datacenter to run stuff. But, that's probably where the most money is.

I wouldn't be surprised if it takes a while to open up to general public where you can dynamically scale up and down though (beyond what e.g. Cloudflare workers provides) due to the capacity challenges I mentioned elsewhere.
The weight is more of an issue. Heavy lift helis cannot lift a fully loaded 20ft container (weighing up to 67,000lbs), let alone a 40 footer.
Skydiving from the Edge of Space (2012)
Raising the banks for say 1/2 mile on either end of the ship might not be impossible? Maybe?
> The ties are interesting and deep.

Brad! You're alive! In case you hadn't heard: libfossil was recently revived, has been brought up to date with regards to SHA3 hashes, and got both "update" and "revert" APIs within the past week or two. The "last" major day-to-day feature it's missing is merge. We have the merge algo (it's used by update), but not yet the equivalent of the merge command. Your account is still active on the repo (https://fossil.wanderinghorse.net/r/libfossil).
This isn’t the worst idea in the world. It’s just not a long term or future looking plan..
> I don't see JWZ stepping up to triage random bugs in GNOME, probably because he knows it's a thankless job with no pay that he wouldn't enjoy.

Thing about it is, it's the responsibility of the GNOME project. It's the responsibility of the developers that sign up to it. Each time GNOME has been improved, old problems still persist. It says something about a project and the integrity of the developers when they claim to increase usability and yet do not bother with longstanding problems.

The root of the problem is a certain mindset to development. One that is numerous and yet flawed.

"Move fast, break things! No time to fix them we have other concerns like- checks notes- revising every system menu to look slightly different. Hell yeah!! Wooh!"
> fear of running afoul of ever changing--potentially ex-post facto--rules.

And if it’s not clear, that’s a feature, not a bug.
Not that many people who use Linux are clamoring for it, but it's interesting that GitHub does not provide an official desktop app for Linux -- even though it's a frickin Electron all. And that's totally GitHub's doing.

Meanwhile, at the parent company, Microsoft offets VS Code for Linux. And it's nice.
But naively, I’d think you just need to apply the opposite force to the force that got it stuck. Surely that didn’t break the hull.
1) Stories like that, where 2000 years old historic injusticies are discussed, remind me of the Trial of Socrates..

The trial of Socrates was held to determine the philosopher's guilt of two charges: asebeia against the pantheon of Athens, and corruption of the youth of the city-state; the accusers cited two impious acts by Socrates: "failing to acknowledge the gods that the city acknowledges" and "introducing new deities".

https://en.wikipedia.org/wiki/Trial_of_Socrates

..which was 'repeated': https://www.onassis.org/whats-on/new-trial-socrates

2) This guy just wants to make a name for himself, he will be invited for interviews etc. It would make 'some' sense to have this in a philosophical/theoretical/acamedic context, in a way how university teams debate for A vs B. But this is just rediculous..