skysight-inc/HackerNews huggingface dataset:
Can you compare this with the alternative of creating a lightweight alternative repo with, say:

git-clone --reference /existing/local/repo
Counterexample: I'm lacto-ovo vegetarian but not vegan partly because the anxiety and stress involved in checking ingredients for ethical purity, or worrying about honey or bone-bleached sugar or rennet in cheese, is not good for me.
Was Coinbase the company that paid-off employees to leave when it implemented the "no politics at work" policy? I had my suspicions that this would result in chilling /suppression of dissent as "politics".
Truly great GUI design is very challenging. I've used very few applications which I think have a truly great UI that beats the CLI in terms of the efficiency of presenting options in orthogonal and conditional ways (orthogonal: two features which don't interact at all can usually be programmed independently and appear in distinct locations, while conditional: options that are only valid if another option is set to a specific value).

The best UI I've worked with so far is Fusion 360. Like most 3d modelling tools it has a fairly steep learning curve, but it does a fantastic job of making your life easier. It has a bunch of UI dialogs for parameter setting (some of which are better than others) that do a good job with both orthogonality and conditionality. I really wanted to like blender but just about everything in it feels rotated 90 degrees to how I'd do it.
My impression is many new bloggers are among the ones who have never heard about RSS.
Including Tailwind’s list of colors in an scss codebase is trivial.

Same for spacing and font sizes if you need these standardized and haven’t done it already.

Which we always did way before tailwind was invented.
Adafruit has done to Arduino what Arduino did to Wiring. Adafruit is pushing it's own custom python called 'Circuit Python' for it's new hardware so there is no Arduino code examples to go with thier products anymore which is a big disaster.

We should stick to standard Arduino code that should run on all compatible Arduino devices.
What is cannabis software?
One week for each year of service is pretty standard unless you’re getting packaged out for exceptional circumstances (physical office closing/moving, etc).
The second paper you are referencing is not quite what you think it is. It is the application of a neural network to the processor itself, to assist in performing physical register renaming, at runtime, in order to achieve out-of-order execution. This is a very different problem than a compiler's register allocator (for one you're dealing with hundreds of potential registers vs like, 16-30.)

On that topic, NN for branch prediction are, in some sense, nothing new; perceptron and perceptron-based designs have existed for at least 20 years. But I'm not aware of anything concrete or specific in current BP designs as of recently (beyond marketing hype) but I haven't kept up with it; maybe some variation of TAGE with model-assistance is out there, but I'm not sure.

I do not know what a training set or neural network model for performing register allocation on real-world programs would look like at this moment.
Vanity clothing sizing leads to real life changes in clothes measurements too.
Conversely, it is crucially important that we maintain protections on trade secrets, including profit margins, negotiating tactics, distribution agreements, wages, engineering practices, etc.

Information asymmetry must never benefit the individual.
Thanks, did not know about this shady history.
you.com let's you select the sources and apps you want to see more of in the appstore you.com/apps
Both ffmpeg(1) and openssl(1) share that they're meant, or used to be meant, as examples/demos of the underlying APIs. No one was actually supposed to run an actual CA with openssl(1), for example. Both also share that some things are vastly easier using the API than bending over backwards thrice at full moon using the CLI, but because using the API has more friction to it, people generally stick to the CLI (almost) no matter how hard that'll make things.

Oh, and just like you have to know a ton about how media containers, streams and codecs actually work to use the ffmpeg API, you likewise need to be a crypto expert to use the OpenSSL API. Almost the same is true for their CLIs as well, though.
You say:

> resistant to catastrophic backtracking despite features which normally translate to nfa

I interpret this as you equating NFA with backtracking engines, which would be incorrect. Is my interpretation wrong?
Some of those people still are.

Others are not.
That's possibly true, but look at the known superspreader events: Pride event in the Canary Islands, a bathhouse in Madrid, etc. These outbreaks are not associated with heterosexuals with STDs.

In the scientific community the fact that M2M are the dominant spreaders is not disputed. It's only in public discourse that fact is suppressed.

This isn't meant to cast blame, but OTOH if we keep dancing around the facts June might not be just Pride month, but outbreak month. People should be fully informed so they can make their own risk calculation.
Is very risky sexual behaviour a good or bad thing? I'm just seeking to further understand this point.

Any gay saunas in London has lots of big anonymous group sex, if this the idea that risky sex is bad then these types of places would be shut, however they are still open for business.
OP does say system software, and although Erlang can have amazing uptime, I'm not so sure about it's raw performance story (on the other hand, I do remember seeing some insane benchmarks from a elixir framework, so, maybe I'm wrong).

Also, other than Erlang and Elixir, which other reasonably mainstream language has this as first class features? Even Rust doesn't really put queues and message passing front and center, it just makes it easier to get away with doing traditional thread programming.

Things can be old in years since discovery/invention, but still in it's infancy in usability and adoption.
Oh yeah, in grad school we submitted identical proposals by substituting a few paragraphs in the introduction:

"Multifunctional specific chemical probes for AMPA receptors, which are implicated in the pathology of:"

- "Alzheimer's Disease" (NIH)

- "Schizophrenia" (NIMH)

- "Addiction" (NIDA)
This also exists for Python! It's called Gooey, and mimics the argparse standard library module.

https://github.com/chriskiehl/Gooey
The pro-rated version is irrelevant, since the comment was talking about board salaries going down in order to fund higher salaries elsewhere.
Python is a default but it’s hard to make more specific recommendations without knowing the problem domain. Being in government doesn’t make much of a difference.
The demographic trends we're seeing now (declining birth rates for affluent people in the developed world) could be due to our natalism level being mis-calibrated for our current circumstances.

It's good evolutionary strategy to reduce the birth rate to compensate for successful reproduction (i.e. more pregnancies that result in offspring that reach child-rearing age themselves), as otherwise populations will explode beyond the carrying capacity of the environment (or pay more of the fixed resource costs of raising children than is necessary).

What we see now, however, is that in situations where both pre-adult and maternal mortality rates are exceedingly low (such as has been the case for the last ~4-5 generations in the developed world), the strategy undershoots the replacement rate.
SIP is the basis for VoLTE and VoNR. So in some sense iOS and Android still support SIP.
try this one:

https://www.reddit.com/r/photoshopbattles/comments/9w663a/ps...
I personally don't find Toronto or Montreal subways unbearable (warm, but not crazy), while my time in the London Underground was absolutely miserable - I'm not sure how locals handle that kind of stifling heat. Actually, there was one time I was in the old Toronto Osgoode (pre-opera house) station with a -30 degree wind blowing through - that was chilly!

Actually, I'm kind of sad that Montreal has so few cars left that play "Fanfare" [0]

[0] https://web.archive.org/web/20090823173621/http://observator...
It's interesting that you choose Swift as an example, because I think in some ways Swift does a poor job of accommodating async using the "bubble wrap" approach.

Specifically I am talking about the default of using atomic reference counting on all references. This makes it somewhat idiot proof at least with respect to avoiding NPE's, but it comes at a huge performance cost (especially on x86 which I guess is becoming less of a concern for Swift code).

I think this is a fundamental issue: a big part of the benefit of concurrency and parallelism is supposed to be increased performance. However a lot of the ways to make concurrency "generally safe" tend to hamstring performance, because you have to protect against all the different types od errors programmers can make, which basically means a lot of expensive synchronization.

Maybe there is a way to hide this completely, as you say, in a performant way. To do this, I think you would almost have to have either some kind of really clever risk-free data structures, or else a very smart compiler.

Another approach might be to keep concurrency at arms length from the average programmer. I.e. hide 90% of it inside of libraries, and expose safe interfaces which the programmer interacts with in a mostly synchronous way.
ummm. Could this flaw be attacked via the web? And Apple cannot fix it?
My prediction, tangentially: The next evolution over Git will happen at GitHub.
GitHub (and to a much lesser extent, GitLab) is really what allows Git to monopolize the VCS landscape these days, and it's been true almost from the start. GitHub was really Git's killer app; before it was popular, there was still uncertainty about whether the winner of the VCS wars would be Git, or Mercurial, or Bazaar, or whatever. GitHub was what helped Git win that war.

Nobody will be able to break Git's hold over the world except GitHub itself, unless they are able to disrupt GitHub entirely. The player in the best position to do so is Microsoft. They can sneakily launch a competing version (without cannibalizing their own product) within GitHub itself, allowing repos to be selectively "upgraded" to it, and even two-way-mirrored so that Git users can continue to use it until they're ready to migrate.

I think Git will relatively easy to disrupt on technological merits as we slowly (very slowly!) move away from old ways of doing things. The current development cycle where individual developers hack away at their local repo and then submit patches already seems antiquated; meanwhile, teams are collaborating in realtime in apps like Google Docs, Notion, Figma, Miro, etc. We have already started expecting our collaboration tools to be "live". Why shouldn't code be the same way?

The other trend we see is the need for code collaboration tools to become more integrated. Git is essentially a glorified file system that happens to have good undo and diffing tools, and the workflows around building, testing, project management, etc. are comparatively primitive for what we developers actually need. For example, right now I do commits locally, then push to a branch, create a PR, and wait for it to build and run tests, then look at the failures, and go back, do some more commits, and rinse and repeat. Why can't the build happen while I'm writing the code, so that I have instant feedback rather than having to go through these manual, multi-step processes?

In particular, we see tools winning over other tools when they reduce friction. I think that's where the next iteration of version control and code collaboration tools will find its way in.
> board salary go down a bit
I have worked with smallstep and I can't say anything but amazing things. It's a top quality project with clear doc and great UX. I really wish we had many more projects like this. Kudos guys, kudos.
At least back in my day, thread hi-jacking was kinda frowned upon. You kids are like aliens to me.
Weird take. Sure, you could try to re-build what you had before the apocalypse. Or you could build a new world that isn't the one that just plunged everything into chaos. If our technology wasn't so good, the world wouldn't be as populated, we wouldn't need so many resources, there wouldn't be so many ways to poison the earth, and the earth would be habitable and sustainable for millennia.

After the apocalypse, I want the people who can dig wells, practice permaculture, organize a farm, keep sheep, spin yarn, blacksmith, prep lumber, fire pottery and glass, tan leather, hunt, fish, manage woodlands. Doctors and scientists would be handy too, but now that we know so much about how biology works it wouldn't be so difficult to keep people living longer. Assuming antibiotics still work in 20 years and we retain some basic surgical skills, we're basically set.

The most challenging thing after an apocalypse is obviously going to be government. If there's no law and order you can't really organize anything. Whoever has the most power, best strategizing, and most flexible morals will collect the most resources and gather the largest forces. It'll be "join or die", and slavery will come back. Just read your history to see what happens when societies crumble.
Google still has options (which, granted, they've exercised) including adding more remote offices.

They don't want to do that because they've already spent a bunch of money on their fancy HQ and don't want to see it empty out.

There are plenty of employers with < 1000 employees, however, crowding these downtown areas. They have way more flexibility in being able to move out of these city centers and into more affordable locations for everyone. They don't because part of the reason for their offices in these downtown location is rich people showing off to other rich people. You gotta "look" successful.
I disagree. Not only did the intervention help no one but the banks, but when they were bailed out with taxpayer money, they were refusing loans to the point they were sued over it. While using the same funds to pay obscene CEO bonuses.

We stopped having a free market at that moment, and we've seen things go right back to the same exact spot only worse.

Our entire financial system is bullshit now, it's one huge moral hazard.
Is there a way to get rid of results with listicle titles like "8 Best Toasters to Buy in 2022"?
Is there some specific reason I am missong or just that you prefer cash?
> Work with 3 incredible guys that I trust

Do you actually trust them? It sounds like they haven't lived up to what you feel was promised in terms of helping with the GTM and getting the business off the ground.

You gave up control very early for money. Who knows if it was a good decision or not, but if you aren't at peace with the deal you made that is a very shaky foundation to be starting on.

> While the time with them is very helpful, I can't shake the feeling that if I'm doing 99% of the work + came up with the idea, I'm better of finding a co-founder and start my own company.

Since you are not CEO, presumably they own your IP - so your options may be limited with striking out on your own.
https://archive.ph/pIN9V
>I think your problems must stem from astounding levels of corruption.

Yes, it's a pretty astoundingly corrupt city. But stamping out corruption is one of the fundamental components of good governance.
This but instead as a "WTF are you trying to do?" wizard that left out options that are very obsolete or entirely a bad idea, would actually be cool. Start with the goal rather than the "how".
I never noticed that trend. None of my coworkers do woodworking specifically, some know enough not to mistake wood chisels for screwdrivers, and they may actually be rather good at it, but it is out of a wider set of skills that may include masonry, electronics, sewing, mechanic, etc... the usual jack-of-all-trades hobbyist crafty kind who do stuff themselves.

I can think of a few reason why software engineer appear to like woodworking.

- They are overrepresented on the internet, me, a software engineer who mounted a shelf a few years ago is more likely to exchange woodworking tips on the internet than my granddad who was an actual 8 fingered woodworker.

- If most of the people you know are software engineers, the ones who like woodworking are likely to be software engineers too, a simple statistical bias.

- Woodworking is technical work, software engineering is technical work, it is more related than, say, team sports, dancing or organizing birthday parties (some software engineers do that too of course, but it is not something they are known for).

- Software engineers earn the right amount of money for that kind of hobby. Woodworking is rather expensive, good tools are not cheap, neither is the space your workshop takes and the wood, especially now. But is not as expensive as racing cars and flying helicopters.
As a computer science student (Informatik over here), I have to say that my university program was heavy on theoretical CS and maths, but there was extremely little in terms of hardware or low level engineering. The one networking class I took diving into the internet stack was probably the closest to it.

Obviously everyone's experience will be different but I think of a CS education more of treating computers like an abstract machine, not a physical one.
I would say proper attribution and credit is even more important in open source development than elsewhere.

My day job takes credit for my work, but compensates me in money. Pretty much the only "pay" for the vast majority of open source work is credit.

> it's hard to argue that Massimo did wrong to the community by popularizing Arduino

So who made that argument? I haven't seen anyone claim his marketing efforts were unethical.

But let's say you wrote a significant part of a book. I took your work, completed it, and published it as solely my work. It becomes wildly successful. Have I done anything wrong?
Unsure of novice, but I have this book[0] which is pretty great.

[0] https://man7.org/tlpi/
>then cryptocurrencies are not for you.

What this means to me is that cryptocurrencies are not for anybody. We don't have to create digital systems with the limitations of cash. We haven't had to do that for decades. Now there's a push to go back to the time before that, for (in general) no discernible reason besides people gambling on the price.
At the level of a person? It's an individual decision. This is why I think the actual facts of monkeypox transmission should be openly discussed. If someone is in a monogamous relationship with another then unsafe sexual practices are limited in terms of risk. Other situations may be different. People need real data to make their own risk calculation.

At a societal level? History says yes.

EDIT: I would note that during the peak of the AIDS epidemic government did close bathhouses.
I suggest approaching this issue from the other angle - which alternatives are worse than whitelist/blacklist in your opinion?
i'd think the primary killer for mush would be the authors refusal to allow porting to X11
You are right, but that doesn't seem like a good excuse to remove that information from the Play Store completely. It would be trivial for the Android APIs to require that all permissions requested programmatically are also present in the manifest. This would continue to give user's a picture of what the app could/would request.

They could just change their play store listing from "Required permissions" to "Permissions this app can request". This is similar to the "nutrition label" approach that the Apple App Store has.
Haha no, it actually didn't occur to me when asking.
A+. Nothing more needed to be said.
This is anecdata but two high profile tech layoffs you've read about on here in the last few years gave out more like 2 months per year served, on the low end.
Jesus, I just realized how amazingly clean and dense UIs really can be.

Radios, checkboxes, sliders, complexity hiding tabs, help on hover (not shown), error messages on invalid inputs, making invalid inputs not representable in general etc.

Imagine every cli tool having this kind of mock ui as playground that spits out cmd line command with args - as help tool/whatever as alternative to medium sized book text help.
It is still an incremental/lazy DVCS, the first checkout does not download the whole repository, but for most users it looks like a DVCS.
Thats also fine, especially if priced drop more. But even in a sane economy I would expect most would get raises as they work faster and better, even as prices fall.
I was unaware monkey labor was even a thing and Chaokoh is my preferred coconut milk brand, so now I have to ask myself: do I care about monkey labor? What's the alternative to monkey labor in the coconut industry? Is monkey labor depriving human laborers of paying jobs; is it protecting them from a dangerous task?
see also Starship Troopers (R A Heinlein) - a short story aimed at a particular audience perhaps but makes explicit this concept.
"The best 3 skins are going to receive a Gameboy Advance" is just perfection.

How did you implement it? Was there some kind of API you could hook into to extend iexplore? Sorry if it's a dumb question but I don't know anything about windows programming.
https://archive.ph/3JCv4
The Wii U also needed to be backwards-compatible with the Wii, which used the bespoke paired singles and locked cache line features of the GameCube's PPC 750 derivative. This almost certainly locked them out of newer PowerPC designs without more engineering work than Nintendo would be willing to put into its systems.

For context, Nintendo has always been weirdly quirky and low-buck when it comes to core silicon engineering. The Switch is a Tegra X1 in a trenchcoat, the SNES used a 65C816 at about half the clockspeed it needed to be[0] and had half the VRAM removed at the last minute, and the NES stole[1] the 6502 masks so they didn't have to pay MOS for legit chips. All of those design decisions were made purely to improve margins and genuinely constrained game developers in the process. "Lateral thinking with withered technology" is kind of just their thing.

At least now they're 100% on board with a silicon vendor with a sane roadmap, so they'll at least have a steady supply of backwards-compatible last-gen chips to repackage.

[0] At least it wasn't as slow as the Apple IIgs they pulled it from

[1] Technically legal as IC maskwork rights did not exist yet. This is also why decimal mode was removed - it was literally the only thing MOS had a patent on in the 6502 design.
> I think in some ways Swift does a poor job of accommodating async using the "bubble wrap" approach.

I agree. Async/await has a "kludgy" feel to it (to me). It's "added on," not "embedded in." But I'm not a language writer, so I don't have alternatives to offer.

I was talking about how it does generics. I think it does that quite well.
I think I've commented before on this but I've had great success using VSCode Remote Containers. Essentially using the M1 as a frontend to an x86 environment.

Works great and I can move between a local and cloud servers depending on requirements
I'm glad that Rust has changed this, at least in my very specific case: I wrote a command-line application in PHP and adding parallelisation was a long journey of trial and error and concurrency bugs that took over a week to get right.

I rewrote the same application in Rust. I followed the Arc/Mutex documentation and parallelised it over a few hours. It worked perfectly.
"Just as well" is very relative here. For people who are truly competitive 100ms is enough to create a massive disadvantage against someone of similar skill.
I was just wondering if this existed yesterday. LetsEncrypt is out there for real certs. I need a site cert for local development. Why can't I type my hostname and mash one button?