skysight-inc/HackerNews huggingface dataset:
That's pretty common. The "browserslist" tool allows you to specify which features you want to support in terms of the browsers that support them, and the default is "> 0.5%, last 2 versions, Firefox ESR, not dead", supports all browser versions for which at least one of the following is true:

* Have more than 0.5% market share

* Is one of the last two released versions of that browser type

* Is the Firefox LTS release, which presumably doesn't fit the previous two rows but is deemed useful and modern enough to support.

In addition, all "dead" browsers (any version of IE, and a handful of obsolete mobile browsers) are explicitly not supported.

Of course, the browserslist string can be configured as needed, so if you know all users will be using a certain browser (say in a corporate environment) you can configure that fairly easily, and you can even use your own stats for things like the >2% queries.

This string can be translated into a list of browsers, and then that list of browsers can be translated into a set of supported features, which you can use to warn developers if they use unsupported elements, or pass to the bundler so that only the relevant polyfills get included. There are also more advanced techniques (like building a modern and a legacy bundle which can be loaded as needed depending on the browser).
There are also deserts with rocks and not sand. The Sahara in most of its stretch is more rocky than sandy. Arid and desert climate are synonymous.
Kosher, halal, whatever. Have middle eastern people heard about hygiene and freshness of meat? I don't need food with your voodo.
I've worked at places where they would "solve" this problem by letting the build break while all the commit in various repositories land all at once. It's really bad.
I don't see anything better, or even close
I wonder what the countermeasures to these will be. To construct your drones and missiles out of highly reflective mirrors?
So you want to learn electronics? I suggest that you take the time to actually learn the theory behind it and learn how resistance, capacitance, inductance affects the system. It is hard but helps a lot. If you want to understand digital systems, then learn how digital basic components work and how you combine them to create more complex systems. Had electronics as my major in my bachelor's degree, and the mental model is really important when it comes to electronics, and the only way to really understand it and get the correct mental model is by repeatedly analyzing the networks and the change over time (resistance,capacitance,inductance) and all of sudden it makes perfectly sense!
Compilers, tools, libraries.

Also things such as flight software, aerospace controls, hardware. Plenty of industries where their hardware needs to run on low-level to keep costs low (both in material and energy consumption).
It generally gives the sense that mono-repo is actually irrelevant, and the more detailed processes across the whole experience are what matters.
The agitator was just transferring the volatile materials in the safest way possible. Safe non-flammable helium, low chance of collision compared to roadways or rail, material can't sink into the ocean triggering sanctions.
Imagine you have two teams in one monorepo and requirements.txt has pinned numpy at 1.22. One team wants to upgrade to 1.24 but the upgrade breaks the other team’s code as it was dependent on an emergent property* in the older version of numpy.

How would you handle this situation as an IC? As a manager of one of the teams? As a skip-level manager of both teams?

As a budding IC on the team that wants the upgrade, you may want to go fix up the other team’s code for them so you can bring them along with the upgrade. Realistically, the further you get from Google’s level of engineering discipline and skill the more likely you are to encounter the following in the needs-1.22 codebase:

- horrible code that is hard to understand and therefore hard to refactor

- code with no tests, making it risky to refactor

- the team that wrote it have all left or been fired and no one is available to help understand it

- they are a remote team with no social relationship to you who interact entirely online, in writing, in the style of an aggressive subreddit mod

- deeply entrenched factions mean that even if you offer them a patch they will default refuse it because who are you to work on their codebase and they don’t need the upgraded numpy so why should they waste resources on reviewing something they don’t want

- misguided adherence to status enhancing terms like “audit” and “compliance” mean jobsworth ICs refuse to even look at your patch because someone somewhere once heard a friend of a friend whose company failed SOC2 because engineer from floor X made a change to code owned by floor Y and it went against policy

All of these social problems are real ones I have encountered and if you have solved these then you’re probably already happily in a monorepo already. If instead you work in an org full of teams pointing guns at each other in a fight to the death to stop any kind of cross org collaboration from sullying the purity of the tribal system then know this: it gets better, and if you build the right social connections then the technical efficiency of having your monobusiness executing its monomission inside a monorepo is within reach!

*bug
The first reason is that it is a war crime. The second reason is that it would be trivial to defend against with standard laser safety goggles.
I just got used to using KiCad 6!!

I'm absolutely delighted that KiCad is as usable and continues to be developed on. I remember a time not too long ago where the Mac version was tragically unmaintained. I now do all my EDA in KiCad. I'm not a professional EE. All my stuff is hobbiest, and relatively amateur, but it's so nice to have tools that are so flexible.
two things..

1. that flaccid teeth meme

2. sharks teeth

i would be comfortable with having a fresh set of teeth every other year or 3 or 5 years later. It would mean i could be a little bit more lazy and/or not have to "SUFFER". i hate that, the teeth are the worst
Took me a bit, but my take here is -- satire by someone who's actually completely given up on the idea of making software better? Where you make fun of a goal because, deep down, you believe that you'll never be good enough to attain it? That's the only read that makes this make sense to me.
Managed to stay even for 3 months. Arcane stuff is what I got but I find it sensible.
> At some point we plan to leverage the WASM ABI to help with stability across versions & toolchains and stuff a WASM runtime in there too, so that support for "applications" written in something other than Rust is easier.

the GP was talking about guaranteed low latency execution. You're orbiting a different star here.
This functionality seems to be partially included in the official extension now. There's a "search container name field", but it's not active when you open the pop-up (hence the partial).

I don't know when it arrived, I'm pretty sure it hasn't been there too long, but I don't pay too much attention to this extension's UI. I'm running Firefox 109.
Structure is important, that's where NoSQL fails from the get go. We should stop investing so much time into NoSQL and look more into combining SQL and Graphs
Donald Hoffman: Do we see reality as it is? (2015) [video]
FWIW, I agree with you that # of papers is not going to matter to some hiring managers. Are you strong at coding? When I've hired research engineers, the most important things I've looked for are performance in a take-home coding challenge, and their technical creativity in approaching daunting problems.

Do you have a personal website with a C.V.?
I've been saying this for half a decade. The solution to having to constantly update dependency version numbers is to ensure that dependencies are more generic than the logic which uses them. If a module is generic and can handle a lot of use cases in a flexible way, then you won't need to update it too often.

One problem is that a lot of developers at big companies code business logic into their modules/dependencies... So whenever the business domain requirements change, they need to update many dependencies... Sometimes they depend on each other and so it's like a tangled web of dependencies which need to be constantly updated whenever requirements change.

Instead of trying to design modules properly to avoid everything becoming a giant tangled web, they prefer to just facilitate it with a monorepo which makes it easier to create and work with the mess (until the point when nobody can make sense of it anymore)... But for sure, this approach introduces vulnerabilities into the system. I don't know how most of the internet still functions.
This looks really interesting, why did they stop working on it?
For an individual - HFT isn't all that accessible. Fees gonna kill ya. But yeah - you just zoom out a little bit and work from there.
Afaik, it's still missing a high quality REPL which python can give you. Extremely useful for exploratory coding.

Otherwise I have to agree, Typescript is a pretty damned good compromise.
Maybe retroreflectors?
Make: Electronics by Charles Platt will take you through all the whys and wheres, starting at the very basics. I highly recommend it.

Also, I'll recommend the "Follow the example" approach of just looking at the data sheets for various components and modules. Especially stuff like the Arduino Uno - It's got a microcontroller, and then everything around it is just support. You start to see patterns where there (for example) a 10uF and 0.1uF Capacitor around power inputs. And they're everywhere so even if you don't know why (yet) you do know that you need capacitors around power inputs.
Here’s someone who disagrees, AWS CTO Werner Vogels: https://youtu.be/RfvL_423a-I
His entire Re:invent keynote was on topic of async systems, and why you need it.
It would be good to have more documentation on usage, though; things like how to deal with struct padding (or packed structs), common OS API types (presumably manual munging of UCS2/UTF16 is needed for Windows), etc; at least to mention that it's unchanged from …/x/sys?

It's easier with dlopen because it's still C and therefore you have the normal headers…
Those are a symptom of burgeoning skepticism. Just because people are acquiring newfound skepticism doesn't mean they'll believe all of the optimal and reasonable things. It goes back to normal where much like for all of previous human history, people believed ridiculous rumors all the time.

It was only the last 100-150 years or so that people have really gotten locked in to the single minded ideology wars while totally locking down their sources of information.
You would think after all these years people would stop using the term NoSQL. They are just databases.

Many of the so-called NoSQL ones like MongoDB or Cassandra can support schemas, transactions, strong consistency, joins, secondary indexes etc. And SQL databases like PostgreSQL support schema-less data structures.

And with Presto, Spark SQL etc you can use SQL with almost any data store.
counterpoint: At the end of the day, I just want people to use my stuff. Right now, 99% of what I write ends up MIT because I just want the shortest and most permissive license for others to use what I create without bothering me.

Not to discount the feelings of others, but in a sense I only wish I could have these problems.
David Duetsch: multiverse vs. virtual particles
I admit to being hardly qualified to hold forth on this subject but...

In his book "The Fabric Of Reality", in discussing the odd results of the famous double slit experiment,
David postulates "shadow photons" which interact with the single photon to produce the interference result. He goes on to argue that there must be millions of these shadow photons. Since they don't interact with any known measurement device they must exist elsewhere... From this he postulates that they exist in other universes and from that assumption concludes that the "multiverse" exists.

Given the same experiment, my conjecture differs. It is "known" that the vacuum gives rise to "virtual particles" ( https://en.wikipedia.org/wiki/Virtual_particle ). Indeed, these can be measured, giving rise to the Casimir effect ( https://en.wikipedia.org/wiki/Casimir_effect ). Interactions between photons, especially in their wave-like characteristics, and virtual particles seems a more Occam's Razor solution.

Does the interaction of the wave-like photon and the "slot-space confinement" occupied with virtual particles affect and explain the result? What effect would virtual particles have on the photon wave? Indeed, do virtual particle interactions with "real" particles explain the measurement collapse problem?

To that point, what effect does a "slot" have for virtual particle generation / frequency / wavelength / etc.? Does virtual particle production change due to slot width? Do certain slot widths generate "virtual standing waves" that interact with particles? If the slots were "Casimir-width" does the double slit experiment outcome change? Perhaps "shadow photons" are just inducing "resonant virtual particles" to temporarily exist and affect the results.

The leap of faith from a double-slit result to a multiverse seems a bit too far for me to jump.
Is what you earn so far out of whack with cost of living? How many standard deviations above average for your age are you at present?

Not to disrespect the "can I do better" part

Taking a second job in SWE is risky. You may hit IPR rules both sides and you risk termination at will for perceived disloyalty.

Would you tell your current employer you have a second job? What would you do, if they found out indirectly?
I use this with the Temporary Containers extension, so every tab is a new container, and a new session to the website I'm visiting. When I close the tab/container, all information about that site is lost. My browsing behavior - by default - is cookies live for as long as the container lives (and other cached elements). It makes me feel safer, browsing online, that I have to opt-in to remembering cookies and having them persist longer than the container. I can assign things over to the static containers like work-play-etc. For development I can have several tabs open with several independent sessions/logins going to the same website. When I tried to do this with Chrome it was 'clunky' to run separate Chrome profiles, which seem to be separate instances. I do remember an extension to do multiple in-the-same-browser sessions, but it was using a 3rd party service. I can have multiple sessions going in the same window in Firefox. As I understand, FPI prevents caching being used as a means to spy where you've been. My naive understanding is that containers encompass more than the cached elements FPI segregates, including things like fonts or localstorage. (I'm probably wrong) The only blindspot I see in Firefox is I wish preferences for extensions were per-container as well. I still use uMatrix, so if I've unblocked JS for a domain in 1 container, I don't want it unblocked for the same domain in an entirely separate container.

Also, for some sites where I do "Sign in with Google", I like being able to 'stitch together' those session cookies by opening sites in the "Google" container so i can just waltz right into the "other site". On my other containers, they don't have the session cookie for Google in the background so I'm good. I use this for work-related things with SSO. Instead of naming the "static containers" "Work, Play, etc", I just call them the SSO-provider, and I know if I move an existing container into that or open a new tab using that container it will have the login I need.

My default settings are pretty locked down. Umatrix blocks a lot in my new temporary containers, and then I gradually unblock things.
I think that some users here in the comments are bloody missing the point.

It's easy to figure out what the authors are saying, provided that you guys have something called "basic reading comprehension". Here's a TL;DR: "software is being judged by the wrong criteria. Focus on the users, dammit. Software should be judged by its usability, speed, bug-freeness, and innovativeness." The authors aren't really picking a bone against structured programming (or object-oriented programming, or whatever), those bullet points sound more like the type of excuse for crapware that you'd hear back in the day.

Also look at the references; the newest one is from '94. This text is probably from '94-'00. Tech reference there should be contextualised to those times, not to 25~30 years later aka now.

Finally, the general tone being used by the text is not serious, it's cheeky and troll-ish. Odds are that the authors intended this as food for thought, not as a dissertation that should be analysed and replied with "ackshyually, this specific example is 0.573% inaccurate lol lmao".
Gregory Benford Had a Major Stroke on December 22
In the US at least, basically every bank only offers SMS for 2FA which is absurd
Platform Engineering Teams Done Right
The author lost me at the first few lines :
> In a microservice architecture one needs to communicate between the different services. The golden hammer for such communication is REST-ish services employing JSON over HTTP.

Are people really relying on REST-ish inter-services communications? I have seen very large systems and most of the systems are async/promised based or have an underlying message-queue implementation or pub-sub like Kafka.
I didn't say it did, but when I am looking for a "fast learner", they develop a flow state and collect experience to fold back into their feedback model of learning a new domain.

They are doing continuous hypothesizing and refutation and showing/proving the same result from multiple directions.

My experience with "whiz kids" people is that they have immense raw mental analysis power, but not broad analytical ability and their lack of real world context greatly hinders them. They don't have the ability to synthesize alternative viewpoints, their view of the world is from a monocular distant vantage point.
Pretty sure the setting has been around for a while, possibly upstreamed from brave but I feel like it was around before then. It’s pretty hidden tho, and most ppl don’t want it and get confused why it even exists so it’s possible there isn’t great documentation on it.
Trying to pretend itnis not about that is just bad faith. Of course topic is women dependent and without income rather then males being dependent on women.
Wonder how much of that is going straight into energy execs pockets, never to be seen again.
I have no idea, in my long career I’ve never installed a computer game on anything. It might be surprising, but some people use computers for other things.
Bill Ackman announces foundation funding for controversial ousted MIT scientist
Truncating the Taylor expansion after the first term says exponential y = exp(t) can be approximated as y_approx = 1 which is a constant. This is true if you zoom in around t=0 far enough.

Then as you zoom out, you have to include higher order terms to account for the exponential increase.
I remember reading another interesting article about the widening rules in C / C++ and one of the recommendations was that you could always widen when comparing small apples to medium apples. You'd both widen them to large apples. But not for the 128 one. There is no larger one. If anybody finds the article... I think it's applicable here on the xisdigit example.
If you don’t trust the government to run healthcare you definitely shouldn’t trust them to run the military.
"Print-is-append" is something that I had done, in both ways, because it does make sense obviously. In C, you can use open_memstream to make a variable size buffer to append to, similarly than they have there, and you can use any of the existing functions such as fwrite, fputc, fprintf, etc to write to it. If you want to do your own things with it instead of a buffer accumulation, you can use fopencookie. You do not need to do what is shown in that linked document because C already has such a thing; you can use the FILE object for many kind of streams, both built-in and custom streams. (However, custom streams is a GNU feature, so is not standard C, but it is useful sometimes.)

(I made a library to compute cryptographic hashes, which does use fopencookie and allows to specify a "echo stream", which if specified also copies the data to another stream too. This way, you can write data to a file or other stream and also compute the hash at the same time, without needing to store it in memory.)
i think there is only a subset of knowledge that is accessible when talking to ChatGPT, since it lacks reasoning, albeit faking it quite successfully.

it should be judged for what it is - an amazing language utility, that helps me write congratulatory limericks and generate 10 random heavy metal band names.
There is directory / file level ACL. Due to AI the secret sauce isn't as important as all of the data. Recommendation algorithms don't need to be super confidential since it ultimately turns into "make content that people will want recommended to them."
I'm a big Deno fan and use it whenever I can. I think tasks are great and they solve the most common needs.

In my experience, however, as soon as my tasks section got large enough that a separate file was needed, it became long-running enough that I wanted a generic file dependency-aware builds which required a make-like solution. What should large projects do that need to build assets or perform long-running work as part of a build process without dipping into another clunky tool?

I have similar issues with threading development-only import maps that reference local modules in a polyrepo during development and sharing common Deno configs. Customization doesn't scale well to task one-liners even though I want it to. Do folks know of open-source polyrepo reference that serve as a paradigm for patterns that scale?
long overdue.

> The desire then was to assess nonhuman intelligence by teaching nonhumans to speak like we do—when in fact we should have been thinking about their abilities to engage in complex communication on their own terms, in their own embodied way, in their own worldview.

but what can you expect from the species that created bee movie. of course bees’ lack of human speech could be viewed as a lack of communication ability.

and most humans haven’t the slightest what they are communicating through vibration and position. so why would it be considered communication when a bee does it?
> The key here is "if you want the relationship to last." In many relationships, people lose the desire for the relationship to last. For instance, in his contractor anecdote, he cares more about the outcome of the construction project that he cares about prolonging his relationship with the contractor. Or in the case of a business relationship, business partners want the business to be run in their own way more than the want their relationship to stay strong. Everything comes down to a desire to keep the relationship going.

There is also another aspect to the "desire to keep the relationship going". It is culture. It's unfortunate that he used a business relationship to drive home his point, because western business culture greatly emphasizes short-termism, binary outcomes and litigous behavior all of which are not conducive to long-term relationships.

With personal relationships, the same is true: consistency of behavior, personal autonomy and personal goals are all emphasized over collective concerns. These values all make it difficult to value or sustain a 'long-term' relationship that doesn't involve any direct personal benefit.
Meanwhile in 1996 with HP-UX 10.24 update.

https://en.wikipedia.org/wiki/HP-UX

https://community.hpe.com/t5/security/hp-virtual-vault/td-p/...
Swami Vivekananda
I've always wondered how private servers were developed. How was the netcode for private servers developed without any documentation? Were there source code leaks that helped?