skysight-inc/HackerNews huggingface dataset:
> Personally, i really like having multiple return values, since being able to give a function multiple inputs but only being able to return a single thing always felt weird - if your require any metadata in a language like Java, then you'd have to come up with wrapper objects and so on.

MRV is nice and useful, and “error as value” languages usually have ways to return multiple values (usually in the form of tuple), but it’s not proper and correct for error signalling, because the error and non-error are almost always exclusive.

In that case, using MRV means you have to synthesise values for the other case (which makes no sense and loses type safety), and that you can still access the “wrong” value of the pair.

> To me, that's an example of "opt in" error handling, which in my eyes should never be the case. The compiler should force you to handle every exception in some way, or to check for it.

That is what Rust does (including a clear warning if you drop a `Result` without interacting with it at all), although for convenience reasons (because it doesn’t have anonymous enums and / or polymorphic variants) the errors you get tend to be a superset of the effectively possible error set.

Though that’s also a factor of the underlying APIs, when you call into libc it can return pretty much any errno, the documentation may not be exhaustive, and the error set can change from system to system. Plus the error set varies depending on the request’s details (a dependency which again may or may not be well documented and evolving).

So when you call `open(2)`, you might assume a set of possible errors which is not “everything listed in errno(3) and then some”, but a wrapper probably can not outside of one that’s highly controlled and restricted (and even then it’s probably making assumptions it should not).
Large plastic owl? Large plastic owl connected to IOT by satellite on a subscription?
If you use io_uring for timeouts, then CLOCK_BOOTTIME is also on its way to io_uring: https://github.com/axboe/liburing/issues/369
A podcast I listened to recently about clock synchronisation if you’re interested from Signals and Threads [1].

[1] https://overcast.fm/+hrS5e2XoU
I don't remember a lot of details, but from memory the software came on a big reel of tape and you dumped the tar archive off it, unpacked it and tried running the Makefile.

This was around 1988, 1989 and the Pyramid was already obsolete but the organisation had a huge investment in it as a 100 user machine with serial terminals so we had to make do.

First thing was to get the tangle and weave programs running. The header paths and library locations weren't completely standardised and even the function signatures were different between machines. There was no "configure" back then, so it was a case of digging through the the compile and link errors, fixing what didn't work and trying again. Once tangle and weave were running the job got a bit easier until it came to the PostScript output program which was a bit of a law unto itself, but I might not be recalling that part correctly.

Once the tangle/weave steps started working, the Makefile assembled everything and install from there was fairly simple. The bones of TeX were written in an intermediate language and needed the tangle/weave pair to turn it into something functional. To fix my adaptations required developing a passung knowledge of that intermediate language, which was half comments and half expressive code. Once I got my head around it I thought it was fascinating but not terribly practical. Then again, I'm no Knuth and never built anything as cool as a computer type setter so what do I know.

There were a few times that tangle and weave did something weird, but mostly that was my adapted code not working as expected. A few revisions sorted those out quickly.

This must have been right at the tail of that era of Unix though, the Sun workstations were easy to get TeX and LaTex for pre built.

The learning experience of trawling through include files looking for the right functions and adapting calls to make them work on that Pyramid was invaluable as a developer later on, not for the Pyramid knowledge but as an education into unix.

Now of course you can copy and paste your error into google and likely somebody solved the problem already. Back then we had the include files and occasionally usenet. It wasn't necessarily harder to get things done but it required patience and time.
From the literature we have read, XChaCha20 coupled with Poly1305 is safe for DARE, ChaCha20 in isolation isn't. We're employing the former.
Except, of course, for the plasticisers within…
I thought Electron application is a web application running outside the browser window, and not what we usually called "Desktop Application".
i would assume that the presumption of fraud would itself lead to greater degrees of fraud with the inherent justification among partisans being 'well the other guy is doing it so this is the only way we can keep up'. that in of itself might not be that bad but if the fraud or perception of fraud has potential to act as a force multiplier for existing instabilities and intra-party paranoias then it becomes very easy to imagine the process dismantling itself. it really seems like the experiment for this decade is figuring out just how much distrust institutions can take on while still remaining functional.
You don't need it everywhere. With both exceptions and error monads, you can have a happy-flow path that mostly leaves out the boilerplate, and handle errors at a reasonable point.

Go forces you to add even if you want to defer handling to a later point.
Right but...how did you extrapolate from indoor lint to all soil and water? What about all the other non-clothing plastic and rubber noone wants to pay for proper recycling or incineration?
The glass ceiling is so transparent that Harry doesn't even see it.
Lying propaganda to divide us. Death to propagandists.
> Not a fan of the tone, judgement, and gatekeeping in this article.

…Gatekeeping? I'm hardly trying to control access to something. I'm preventing developers from having their focus time squandered.

Anyway…

From your article:

> This made me realize that the real value of a daily standup isn’t the meeting itself. It’s the time that comes after it. Considering this, let’s stop trying to optimize the daily standup itself. Instead, use it as a catalyst to get our teammates away from their desks. Use the standup to start a conversation, but trust the team to finish it.

This is oddly contradictory. You concede that daily standups aren't actually valuable. You say you trust your team to terminate the discussion at an appropriate point, but for some reason you don't trust your team to initiate that conversation when they see fit.

How does that work?

> this is a good article

Well… you would say that, wouldn't you? Didn't you write it?
It's usually too late by the time help arrives in an avalanche scenario. If something happens you could have about 15 minutes to rescue your partner(s). You must NOT go alone. Get a course in snow rescue, find experienced people and go with them. Be alert. Always carry a basic avalanche rescue kit: a modern beacon, a probe and a shovel.

And, if you must, you could get a Cospas-Sarsat PLB in addition to your avalanche beacon.
China limits under 18s to 3 hours of gaming per week
Aside, ten years ago most of the pigeons in London seemed to be dirty with feathers sticking out and have manky feet, but of late they do seem a lot healthier. No idea why.
How I got multiple FAANG offers in Europe
That's a fantastic deep dive from Jane Street on all of this. One of the best internal technical interviews I've ever heard.

This talk by Jon Moore is another great talk on time, causality and synchronization, especially where cluster membership is large and dynamic: https://youtu.be/YqNGbvFHoKM
If you're interested in eliminating proof-of-work for ETH, you should really take a look at the proof-of-stake network in progress. Keywords: "Eth2", "proof of stake" and "the merge".

When proof-of-stake takes over, there won't be any miners. The block proposal process is done by stakers instead. Some of the incentive issues with miners still exist with stakers, but raw competitive power consumption isn't one of them.

It's true that proof-of-stake has been talked about for years, but it has picked up momentum since late last year, as the staking network was actually launched.

The proof-of-stake network has been staking real ETH since end of last year, but does not yet handle mainnet ETH contract transactions. It's called Eth2, but that's caused some confusion, because it's not really a second version to run alongside the first, it is the R&D branch into proof-of-stake and other technical improvements, with mainnet ETH expected to adopt it in due course.

So, the Eth1 components have been renamed "execution layer", Eth2 components renamed "consensus layer", and through a series of testnets and API developments which have been quite active this year, a big change called "The Merge" is being worked on by multiple funded groups (for client diversity) of core Eth developers at the moment.

The Eth2 staking network that already exists has demonstrated the viability, and the investment of real ETH in serious quantities has built up some cryptoeconomic stability prior to its deployment as the ETH consensus layer. The time lag is intentional - you don't want to suddenly switch all ETH over to a network with too few invested stakers.
> I’m imagining

Imagination often does not match reality. I have a (non-Gmail) account that is littered over the web, in git repositories and in multiple leaks. I don't silently drop any emails - the only server-side anti-spam measure I have a regexp to reject the usual spam subjects at submission time, which for normal senders will result in a notification to the user. The amount of spam is hardly at a level that would be anywhere close to making Email unusable.
Even if slice is reallocated, the information about new reallocated slice is still stored in variable s. ps is merely pointing to that variable. The fact that the contents of the variable changed does not mean that its location has to change.

In other words, ps is a pointer to a pointer to array data. Append may change the inner pointer's value but that's about it.
This is good stuff, but it's not new. Meanness is ill will, a mental poison that will inevitably cause a person to harm others, but the very first victim is holder of the ill will. I think this was probably very well known even at the time of the Buddha 26 centuries ago. As I get older I seem to be realizing more and more how often we rediscover or reinvent ideas from the distant past. It may be unavoidable, because wisdom is hard to transmit via words.
Afghanistan's Internet: who has control of what?
Power consumption is a function of the voltage squared, but maximum operating frequency drops down slower than that as you lower the voltage, up to a point as GP said. So efficiency defined as f*P goes up as V goes down.

People definitely do that, the voltage you chose to power your chip is always a consideration, it's one of the variables used by laptop manufacturers to manage thermals, and it's also pretty common to lower the CPU voltage so that you can run a desktop system with passive cooling.
And J/cm³. That's usually the limiting factor for phones, I think.
In this case you literally gave a better example “class”, that said in cosmology there is only one universe ours.

The multiverse and other theories of multiple universes nominally belong to other fields of study.

Cosmology is the study of the universe we live in, specifically it’s development.

That’s why we have terms such as the local/near by universe and the observable universe. I find odd that none that that seem to take offense with the former mentions the latter, since grammatically they are identical.
I guess they have an automatic system to do the same thing as your exploit. After they misconfigured Akamai, their system and your system were racing to claim the exposed S3 buckets.
> ... manually hacking down dependencies, or re-inventing the wheel are far worse practices!

Disagree. Allowing such bloat to permeate your codebase, and supporting such practices as this fat SDK, are far worse. Short-term gain vs long-term loss.
In the case of deep-sea predators, there appears to be less bigger consumptive biomass than consumable biomass at present.

Currently, it is probably more advantageous for some luminous predators there than the risk of being eaten.
The optical perception organs are probably reaching an evolutionary dead end down there.
Better eyesight isn't an option.

But everything is in flux, it just depends on the time frame.
Magnetic field perception might be an option.
Are there deep-sea predators that hunt by magnetic sense?

But it's still cheaper to attract the food than to track it in the dark.

How about auditive perception?

Is 'pinging' the prey an option?

Well, one would need some organ that could be converted to ping, which fishes don't have.
Why is the authors name mentioned in the title here? Are we supposed to know who he is?
I think "waste" is the wrong term.
If you learn from your mistake then it's not waste it's experience.
It often happened to me that useless parts of one project were useful for another one. Sometimes even if the previous project was a complete failure
I suggest using Carbon Copy Cloner [0]. I have been bitten by Time Machine corrupting itself and I'm never going back. It works well and they have excellent documentation for pretty much every scenario. And USB backups are bootable. I'm mostly using it with backup to a NAS.

[0] https://bombich.com/
Personally, I gave up on io-ts due to FP complications, and use suretype instead.

In my case, where I was parsing HTTP request body, it just simplifies the code, if I can call a single function, get back validated object of the expected type, or throw an exception if there is a problem.

Global request handler takes care of catching validation exception, and returning back user friendly error on what field(s) failed validation.
Or the kubernetes package manager
It looked liked a fairly straight-forward example of how systemic sexism forced a female officer who wanted to be on street duty into record keeping.

If time on the 100 yard dash were that important to policing, it would be part of the physical requirements - requirements that the woman would have had to pass in order to get to this stage in the interview process.

For example, https://www.uscp.gov/police-officer-training-preparing-physi... says their Physical Abilities Test - which includes a 375 slalom run - must be finished in 3m52s and "The time is the same for both males and females regardless of age."

Recall too that Kathrine Switzer was assaulted in 1967 for being a woman running in the Boston Marathon. Women at the time were deemed "physiologically incapable" or "too fragile" to run a marathon.

That's only 4 years before Dirty Harry came out, and would have definitely been part of general cultural awareness. Note that the portrayed candidate would have started on the force even before Switzer's real-life run.

Also, you'll notice there was a men's quota too - 5 men and 3 women.
Tbh, to me the first one is easier to read. There's less jumping.

But both are terrible. It should just be a bunch of if (...) { ... } else if (...) { ... } else { ...} etc. with no mutation of variables (what are all those v += 1 for?).
This is why I’m thinking of using my domain and aliases.
However if I use google workspace you get restrictions, however for now, these restrictions don’t apply to me as I’m mostly Apple not google, I just like the google UX.
I like your quotes around "non conventional", as everything about storing files in a directory is the traditional and conventional way to store files.
I can only recommend Godot. It's easy to pick up and feels like a consistent and fresh take on a game engine. For Unreal especially, for me, it felt like it would always come to the point where Unreal magic is needed to fix a certain problem. With Godot I've never had this feeling, the things you set out to do just work the way you expect them to.
Overall you get the feeling that the engine distills the best gamedev ideas of the last 10 years into one nice package and I couldn't ask for more.
> Given the responses to this article and the general level of education among the HN crowd,

Yeah.

I expect that the "level of education" is part of the problem here. So many "i yam very smart, I thinks different" people who don't know how far out of their lane of competence they are now. Sadly the contrarian impulse leads them into traps that others have set.
Not bootable with latest MacOS anymore, at least not easily.

But ignoring that: CCC is an excellent backup solution for MacOS. Have been bitten by Time Machine twice. Still use it, but do not rely on it.
The observable universe isn’t the same as the local universe. The observable universe encompasses a region of approximately 13.7B light years from our point of observation which is earth, the local or near by universe is limited to about 1b light years.

Both have their usefulness when conducting observations as we need to take certain assumptions based on what we know.

The former is anything that is currently within our cosmological horizon the latter is anything we can observe that is in the same relative slice of time or cosmological development stage as us.
Realistic options are not limited to "handle at every point of the call stack where an error is encountered" like Go and "end program execution as soon as an error is encountered". Most programs handle most errors by bubbling them up to some top-level event loop and presenting some variant of abort/retry/fail to users. Exceptions are tailor-made to cover this use-case.
I think Autodesk still uses it. I vaguely recall running into some trouble with the FlexLM service and Autodesk Inventor when I still worked as a Windows admin/helpdesk monkey.
That SDK is intended to include support for a bunch of different things, not just login. The actual login can be done in a couple of hundred LoC in PHP using cURL. I've done that for one of my projects. Search for OAuth 2.0 sample code. Once you understand it and get it working, other one-click logins like FB function in pretty much the same way. Adding support for them is trivial.
You are 100% +1 right with scope evaluation !

Still, as all -1 Earth goverments was doing nothing in last 40 years, it is now time to start ! Let it take 20 - 30 years - so what ?

Ok, -2 - China tried to create Windows clone from scratch and failed. Instead MS wrote them social-spying-for-credit system...

Why I say it's govs work and not some company or "startup" LOL ? Becouse of scope or more precise: users expectations.

In that last 40 years just Sun tried to do something sensible and we own them a lot.

So plan should be:

- build on package installable on premise

- many implementations - even few per nations - will not be a mistake. We have open formats in that century...

- client-server model, with server running on host or somewhere on LAN / VPN

- security included from day one, not "to be added later"

- drop http and browsers and rebuild this part, too much bullshit accumulated. After all it's just protocol stack. And we have 30 years long timeframe for it ! Browsers are too stagnated.

- do not include in planning stage peoples involved in "cookie consent" massacre... Looks like listening to American corporations ends like this. Tell them what to do and they will possibly do the best.

- assign funds NOW for next 50 years of incremental development

- make own CPUs, each nation / big company own. And build C compiler for that CPU. Make sure Linux or Minix work on it

Yes, somehow Americans are best with building many things but instantly as they got total control they mess it up. And then keep messing it more !

So let build things, make new good standards and then let Americans join ! :)
No, I don't want to wrap every single statement of my program in its own if-block, thank you very much.
Have you considered using FHE for analyzing the photos encrypted?
I don't work for companies where sales are running engineering. Usually a horrible environment of code monkeys patching shit together so it barely works, and no rest at all inbetween tasks, because sales are clueless about what an engineer does.
If they took no cut at all that'd push the per-stream amount to 0.0057. Still pretty tiny.
What I don't like about our version is that we only focus on small portion of all things in the list (from the OP), mainly the Agile procedural issues.

I think the purpose of having such a checklist is not to limit the discussion to other concerns, but rather serve as a reminder what all the different things can be a problem and should be discussed.
The privacy aspect isn’t a major concern to me, not because I don’t care, but certain services link into gmail better.
I also find that Google’s UX is better for me than others, and from years of using gmail I am used to the options, but was unsure if it was worth “upgrading” to a private domain.
I know the feeling. The goal is supposed to be to improve the process, but often too much time is spent going through the motions rather than meaningful discussion.

In my experience, the value from retros is a function of the skill of the facilitator.

Perhaps you could be a force for change on your team, by speaking bluntly about not spending enough time on that third column. Others might be receptive to it!
Arq.app can backup external disks to most of the big cloud storage providers really well. Unlike Backblaze, they don’t delete these backups if you don’t connect your drive for a specific amount of time.

I’ve used Arq to backup about 2TB of external drives to AWS Glacier. It even let me set the encryption key for the data myself!
This isn't really correct, the original image is always stored in the original place or the place you select to copy it too.
That's why I also think the title is a bit miss leading, cause it was never the Lightroom catalog that was the issue, it was the RAW-images them self.
Does that mean that a) the pointer to the single element is only invalidated on “append” if the slice has no more capacity (this is how C++ vectors work), or b) does the fact that there’s an active reference into the slice always cause a reallocation (copy-on-write style)? If it’s the former, we’re literally in the C++ iterator invalidation nightmare, only without the debugging tools.
You may find it helpful to read up on Poe's law [0].

[0]https://en.m.wikipedia.org/wiki/Poe%27s_law
Thanks!

> Plans to support more DBs?

RocksDB and TiKV backends are planned: https://github.com/losfair/RefineDB/issues/3

> do you intend for the OS community to build the translation layers?

What do you mean by "translation layers" here?
That is what I was saying. Just reasoning just in case, because it was not written.
Threat models are the most important aspects in cryptography and you could include them to support you decisions.
What about maps? Non-nil maps sure seem like they're "reference types", look at [0].

[0] https://play.golang.org/p/xtY_ASExQzR
This analogy fails because distance on a cosmological scale means both space and time whilst on smaller scales we measure space and time as two distinct parameters.

If we go with the single analogy it would be like filtering on Tinder based on distance as well as when the last time that account was active.

It’s like if going more than 50 miles further out of your existing location would only show tinder accounts from 5 years ago which wouldn’t be relevant for what you are looking for which are people who are single right now and looking right now.