skysight-inc/HackerNews huggingface dataset:
Image patch extraction could be statistical rather than semantic. Like if the top part of the image is just all blue sky with no high frequency detail, you don’t necessarily need to feed the model dozens of blue tiles when you could just pass one or two big blue tiles.

If there’s a small plane in part of the sky, an overlapping much smaller tile with that object in it could be passed in as well.

Really just a matter of choosing tile sizes based on how fine the detail is in that part of the image - which is sort of similar to my mental image for how BPE decides whether to cluster characters into one token or not.

But as I say, not a practitioner, and I kind of get the impression that ‘the transformer attention model just solves for all that’.
Could you imagine, Twitter instead of censoring things with AI, corrected people's word usage with that AI? It would be concerning but also kind of cool.

"You mean to use 'accept' rather than 'except'" "You drank an 'espresso' not an 'expresso'" And the French Academy would no longer have a reason to exist.
> Validated engineering cost savings should be treated like sales, the engineer gets a percentage.

If you want to really follow the same compensation structure, we would then give engineers a really low base salary and make 80% of their compensation performance dependent.

Be careful what you wish for :)

Besides - this would drive some strange incentive structures. If you incentivise people based on cloud savings for instance, it will really only be the teams with unnecessarily large cloud spend in the first place that ‘get’ that bonus. If you incentivise on sales, engineers doing great work on back office tools don’t get any cake. Etc.
I think that's a fair take. Tailwind and css-in-js's popularity points to a mismatch between how people want to actually use CSS and how CSS was designed to be used. It looks like people want isolated components, not complex cascading hierarchies.

I think that when :has becomes viable, we will open to the door to CSS-driven declarative UIs as opposed to imperative JS components, but this is pure speculation :-). I believe that a development style that takes advantage of cascading instead of fighting against it could perhaps become one of the new 'schools' of frontend development. I do not think it will become the most popular one, though.
Wrt code, look at the bench in the article. Even with sequential access, you can get a decent speedup using huge pages. But unless you have a good profile and using PGO, it'll likely not be that sequential for code.
Like everything else you'll need to measure it to know exactly what benefit you might get. As a starting point, you can start at looking at the itlb load misses with perf stat -d

Stack access is another story as it's usually local and sequential so it might not be that useful.
In this context I believe that the author is thinking of AC as Zorn's Lemma.

I will try to make a draft of a possible expansion of the reasoning.

Take the set V of functions P(N) -> {Ma,Mi,Un} that for each subset of the naturals classifies it as a majority, a minority, or undecided respecting the conditions in the article.

P(A) = Ma ⇔ P(A') = Mi

P(A) = Ma ⇔ P(A ∪ B) = Ma

P(A) = Ma ⇒ P(A \ {n}) = Ma

P(A) = Ma ∧ P(B) = Ma => P(A ∩ B) = Ma

It is easy to prove that such a function exists f_0 (A) = Mi if |A| ∈ N, f_0 (A) = Ma if |A| = ∞, and f_0 (A) = Un otherwise.

It is harder to prove that there is a such a function that also respects P(A) = Ma ∨ P(A) = Mi for subsets of the naturals.

I believe that to prove this you pretty much have to use Zorn's Lemma with the order f ≤ g ⇔ (f(A) ≤ g(A)) for all A where Un ≤ Ma, Un ≤ Mi, but Mi ≰ Ma and Ma ≰ Mi.

I feel like you can prove that the hypothesis of Zorn's Lemma are satisfied in this case.

But is is easy to see how without ZL or something similar you would have to decide one-by-one how whether each non-finite non-cofinite set maps to Mi or Ma, but there are uncountably many of them to do by simple induction.
Próspera
Does anyone know how to get their hands on a Pi at the moment? Even Pi 3s are going for $100+ on eBay. rpilocator shows everything always out of stock.
That benchmark tests something slightly different with a focus on repeated CSS rules (and all from JS even): it's not surprising that's faster, though it's interesting it's faster even from JS (I acknowledged expecting that, and that CSS rules per HTML element are likely even faster, eg. a td rule with all the styles on it would probably win over that too).

I do get the terseness point, but unless you are completely happy with Tailwind definitions, it makes code less maintainable rather than more IMHO: instead of having a familiar place to look up the "shadow" definition (if that's not really doing what you want) in your own CSS or HTML file, you need to look at tailwind CSS inside your dependencies, or inside a debugging console in your browser.

I am also unhappy about any code where you'd have to write even `class="text-lg"` a 100 times: perhaps I am still living in the foolish dream of semantic markup, and I would hope you can structure your document in a way where styling is context-dependent: so perhaps you put class="text-lg" on an "top-level" element, and then only adjust nested element text sizes where needed.
Yes, they theoretically could. The AMD manual contains this language:

Exception and trap behavior for elements not selected for loading or storing from/to memory is implementation dependent. For instance, a given implementation may signal a data breakpoint or a page fault for doublewords that are zero-masked and not actually written.
The major problem is that they lose money on every burger sold. They have negative net margins. That was never sustainable. It's not quite like a scaling business ala Amazon where you can eventually stop expanding and collect profits. Their entire production process is cost intensive, even if the marginal cost shrinks over time, it is still a loss. So, this was/is no surprise.
> offer free accounts to people

AFAIR, they offer the possibility for a one year free access to a node (Linux/IFL?). I do not remember if it is part of IBM Z Xplore and I didn't find it again with a quick search, but if you contact them they for sure will tell you more.

Edit: I just found https://www.openmainframeproject.org/
We found that the tailwind VScode plugin was hyper helpful along with cutting down the unneeded in tailwind.config. Once you do that, most styling and positioning is variations on sizing, colors, and text sizes. Then the intellisense is pretty helpful to fill in the rest, some gotchas of course. `leading-` is an awful name for line spacing lol. A hardcore knowledge of CSS and all the governance you would use in vanilla is required to use tailwind however. It is important to see it from that angle.

What seemed to help us (and I don't condone this for everyone, it just worked for us) was to go more extreme: No CSS without a bulletproof defense in a PR. The only exception we needed to break in our large scale platform was to style an SVG progress indicator with complex gradients. Angular's behavior around [ngClass] not just adding classes but removing them also was a bit tricky. Personally the behavior in whole feels like a bug but I know it isn't.
Hmmm.. I've had several ExFATs corrupted on their own here. I would concur with its alleged unreliability.

And fsck.exfat didn't fix it so I had to spin up a windows just for that :S

It does show that journalling is really not a convenience anymore but a must-have IMO. Though NTFS is not a good alternative.
Perhaps to cater to people who love meat but won't eat it? What's hard to understand about that? There are plenty of great tasting vegetarian options, now there are plenty of faux meat options as well. The more the merrier in my opinion.
For me it's the exact opposite. I'm a vegetarian for ideological reasons, not health ones. I'm not the healthy kind of vegetarian at all. For me the only flaw of Beyond Meat is that it's a bit too salty and it sits a bit funny (weird-flavored burps after you eat it).

They have a solidly good product, it's a shame they can't make it work.

As a parent one big problem I had with them was that for home use they only sell the huge quarter pound patties (while they do shrink when you cook them, they do so less than beef) which were too much for my kid. I had to thaw them, slice them down the middle (which is tricky) and cook the two halves separately. They're much too big for a standard burger bun. It seems obvious they're going for a prestigious form-factor but missing out on being able to sell something more universal.
Blame statistics for that. Wrong outcome? Well you were unlucky you fell into the 1% error range.

Correct outcome? You totally predicted it correctly.

There is literally no way you can screw up something in statistics and not being able to make up a story to defend your approach.
There's a meaningful difference to my workflow of doing

<div className="px-4"></div>

versus doing

.mycomponent__wrapper {
padding: 0 1rem; // Don't forget the time to look up whether it's vertical | horizontal or horizontal | vertical because I forget all the time
}

then

<div className="mycomponent__wrapper"></div>

and toggling between files, and making sure the team knows my preferred CSS layout structure in the general case.
Plus, the solution for more complicated CSS is to just write it as CSS and to add the class directly like you would before. The point of tailwind is that I don't actually like or care about knowing CSS trivia, I just happen to know it. There's no value to me in doing things directly in CSS unless it's complicated enough to justify going to that layer. A helper layer is perfectly fine.
Signal is more privacy than anonymous.
This was the original, nuanced meaning of "homophobia", before it was simplified in the popular mind (where nuance cannot live) to merely mean "hatred of gay people". I think there was an implicit "see, there's something for straight people in this too!" aspect to the argument -- something like, "by eliminating the taboo on homosexuality, we will also eliminate the negative consequences to straight men of heterosexual signaling ". I'm not sure that's panned out though, since if anything it has probably increased the need for that signaling in many circles.
The dotfiles are for metadata that the non-Mac filesystems can't store. Coloured labels, icon position, longer filenames, creator info etc.

Windows actually does almost the same thing. Thumbs.db etc. And it also creates shadow files for those with metadata when saving to FAT32. You just don't see them on windows as they are hidden, just like dotfiles are on macOS.
Advent of Code will start in a couple of days.
In my experience Data Science is based either on optimizing short term easily measurable KPIs or producing impressive looking BS. So if you're joining a new team and they can't explain in one sentence what they're optimizing for you're probably going to be tasked with producing impressive looking BS.
All those free online .PSD utilities make my spidey-sense tingle.
It's not necessarily my preference but the last few years a lot of my work has been in systems that are just a thin api wrapper around postgres.

In practice the biggest issues with it are that the tooling is significantly behind the state of the art of mainstream dev tooling, both for working engineers and ops. It's also not built with this with style of working in mind, so you accumulate a lot of little struggles that are hard on engineering morale and confidence in the deployed system. DBAs have their own practices, but admin is a different discipline from dev and they aren't always directly compatible.

The other problem is that for most modestly sized money-making applications, the database is the single most resource-intensive and expensive necessary part of the stack. Putting a bunch of business logic in there will never help that, and query optimization is a difficult to acquire skill. You pretty much always end up with just a couple of people who can talk the query planner down off a cliff when you get into the shit.
Interesting, I'll have to read more. From your description it sounds like the problem could be mostly mitigated if you put your glasses on only after sitting down at your desk, and remove them before standing up.
I have to interact with a person who does a lot more than produce code
Medical guidelines that embrace the humility of uncertainty could help doctors
That is so cool, great idea for a game and a platform for playing around. I just did a quick reading of an Emacs Lisp client, and I will look for your Clojure client.
Kotlin, Crystal, Nim, Koka, who can decide?
From an American perspective, French food is as bland and tasteless as your people.
reminds me of robocop movie "you have 30 seconds to comply."
> it can be difficult to have a friend of the opposite sex without people thinking you are intimate.

Is this really a counterexample? It would seem to me to be another example of the same phenomenon.
Disagree, an example with margins (the second example in the article) is not complicated or rare.
In NLP, the simplest positional embeddings are just a sequence of [0, 1, 2, 3, 4, .. n] with n being the length of a sentence. Once you start processing text, you split it into individual embeddings for each word, getting a list of embeddings [E_1, E_2, E_3, ... E_n]. Then you just sum up this embedding vector and positional embeddings vector across the first axis, so each embedding is increased by its positional embedding in other dimensions. This somehow works for encoding position as attention is dumb and doesn't keep positions in mind but you just added some sort of a positional signal attention will recognize. There are many ways to model positional embeddings, e.g. by generating sine/cosine curves etc. You can extend this approach to ViTs.
I think that is not done because it's hard/unclear how to handle patches that are not the same size.

In text it doesn't matter because all tokens are mapped to an integer (eg. the -> 54, hacker-> 1356).
It's goes both ways. There are psychopathic employers/managers and there are psychopathic employees and your average skaters. Skaters aren't always bad and they are part of society and you can't avoid them --but having key ones can rot an entire team.
The author starts with the premise that all abstractions are leaky and then proceeds to show this in the context of using Tailwind. OK..
I don't know how other countries do it, but in Brazil, since 2002, all flour (wheat or corn) must be reinforced with iron and folic acid.

https://memoria.ebc.com.br/agenciabrasil/noticia/2002-12-25/...
Doesnt Harvard receive $m of gifts per annum. Could that influence them??.
Such as ... https://www.gatesfoundation.org/about/committed-grants/2019/...
hmmm https://www.nytimes.com/2009/03/04/business/04pfizer.html
Awesome, thank you.

Sad to hear about the hackerspace. But love the logo : D

Its kinda nuts how much better it is than the original, for all the reasons you mentioned here and in the previous post : D
Given the influence of information technology today, every organization is at risk of a data breach. Learn how to protect your businesses by implementing the Principle of Least Privilege.
To start, it's ok to not like Tailwind. The author's complaints are valid in the sense that Tailwind doesn't really solve the edge-case problems they apparently have.

But the author finishes by saying "Maybe you really want to avoid coming up with names." And yes, I really do want to avoid inventing names and I'll tell you why.

If I have two projects both written in Tailwind, it's trivial to switch between them and make confident adjustments. On the other hand, if I have two projects with `.btn.btn-small`, there could be an infinite number of parent styles affecting that button in unpredictable ways. I don't just need to understand what `.btn` and `.btn-small` do, I need to understand _all_ of the parent selectors which could affect that button. The moment you write the equivalent of `body.single-page .entry-content .btn.btn-small {}`, your code is essentially unmaintainable.

All abstractions are reductive – the mercator projection sucks compared to a three-dimensional globe – but some abstractions are useful and Tailwind is very, very useful to me.
TIL readline has macros.
First we have lot of studies based on statistics.
There are also simple statistics which show than vegetarian live longer then meat eaters.
Then we have the five blue zone where people do not eat meat and most of them are centenarians.

But some people do not support their habits to be changed and are ready to believe anything that confort their opinions.
Even if their habits destroy the planet.
Ask HN: Have you noticed a significant increase in quality with GitHub Copilot?
I have been using GitHub Copilot (in VS Code) since a few weeks now, and have noticed a significant uptick in code generation quality since ~1 week, namely:

- Better clipboard handling: What you copy and paste seems to be included in the generation context.

- Better context handling across different files: The previous files I visit seem to be accounted for in a better way than before.

- Better handling of edit/insertion history: If I am doing some repetitive text insertion, one-shot guessing seems to have been improved, at least to compare with before.

Overall, it feels like context handling had a major overhaul. This could be due to an update to the models, to how context is handled in the frontend, or both. It could also be an illusion due to me getting better at working with Copilot.

Did you also notice such changes?
I can confirm. Set and forget all the way. Works very well on iOs and also on Samsung smartTV (those are evil without some form of Adblock!)

Hardest part for me in the set up was that ad guard should query my router for local domain, because that one keeps track of which dhcp IP address is owned by which host. (This way I can always use host names on my internal network even for devices that get an address via dhcp. Very convenient if you play with Pi Zero and other toys)
You don't look at single outcomes with statistics.
What an awesome site.

My current music project is based around building up layered droning sounds using cassette tape loops. I’ve been using AM radio tuning noises and modem noises. A big part of my influence has been finding old, obsolete, extinct sounds and making them come alive again.
Was that the last stream playing? That control should be connected to that stream, if so.
I am glad that this article emphasizes the messiness of the bipolar junction transistor, but also disappointed that it doesn't engage with the "obvious" question I had back in the day, when I was taking high school electronics, and also doing hobby electronics (this would be early 1980s....)

If you've worked with them at all, you know that bipolar junction transistors are not symmetric -- if you put them in your circuit with the collector and the emitter reversed, then they don't behave the same as if you put them in the right way. Hobbyists know that the schematic-diagram symbol always has the arrow on the base-emitter leg, and the arrow points from P to N.

But the BJT diagram in this article and in elementary textbooks is symmetric -- there's no physical structural difference between the collector and the emitter in the picture.

This isn't necessarily bad, simplifying the problem to illustrate the fundamentals is a legitimate pedagogical technique.

The "obvious" question is, what else is going on in real devices?

I think the answer is that actual commercially-available discrete BJTs are fabricated on a planar substrate, the same way they're done for integrated circuits, and then cut out of the wafer and packaged for individual use. In this process, the collector (I think?) is generally the lowest layer on the wafer, and is much larger than the emitter, which is on top, and is generally much smaller. In the planar case, there's an obvious geometric asymmetry that explains the device's asymmetric behavior.

I'm not 100% solid on that explanation, and I don't recall where I saw it, but this is the kind of next-level detail that I would have liked to see from the article.

(Minor edits for clarity.)
The EU Released the First-Ever Set of Ethical Guidelines for Human Enhancement
It's more complicated than that though.

Alternative "assets" like crypto gained more credence when rates were low. Bond returns in such a regime were not attractive, equity markets rallied to elevated levels, and there was little incentive for debt issuers to use free cash to pay down debt that could be rolled out into perpetuity.

The Fed essentially held the cost of money near zero and that had far-reaching effects.
> Also, most FAT corruptions will cross-link together different chains of different files

Made me smile :) I remember this particular message, from the time when Flip destroyed my disk.
My impression (not based on anything firm) is that basic reasonable-length CRCs are extremely unlikely to have collisions, unless someone is deliberately trying to create collisions. If I were looking for insurance I'd turn to one of the fast 128-bit non-cryptographic hashes.
See? “Better luck next time”.

Not being mean to you, just showing how typically the goal posts are moved.

To give you an example from physics, if you find just one experiment that goes against your model, you immediately invalidate the model. You don’t just make grand claims that the model in general works.
Why some tech CEOs are rooting for Elon Musk
Honestly I just don't see how it's possible to 'forget CSS' with Tailwind. I mean, the classes mostly map 1:1 to CSS properties.

As someone who has been writing CSS for approximately a billion years (actual number more like 13 years) I'm a fan of Tailwind and don't see how it's a 'beginner' thing at all. It solves real-world problems building web applications, and actually many of those problems only come up when you're building large, long-lived applications with many contributing developers which is precisely the kind of thing beginners aren't in charge of.
Millions of paid-only users here on a tight to the styleguide platform we built on tailwind with a team of FE devs with > 10 years experience each: Works great, HTML is easy to read instead of cross referencing classes, bundle output size is dramatically smaller. I'm not saying it is all sunshine and unicorns, just there are different perspectives, gains, and losses.
> Converting a gas appliance to a heat pump, for example, would draw 4 to 6 kW, while an L2 charger for EVs would be 12 to 14 kW. A

This article has an issue with numbers here clearly. A heat pump isn’t really going to consume more electricity than the AC it replaces (and hopefully it is more efficient than the cool-only-AC it replaces as well so electricity uses decreases in the summer).

For electric cars, no-one needs 48A (11.5kw) charging (unless you bought a hummer EV and then you’re an idiot). The city can start denying permits for charging at more than 24-32A unless you have enough battery storage to cover it up.

Palo Alto also does not have TOU plans, and no demand charges.
It is. It's also the reality we in the US have to deal with. All of our infrastructure is in trouble, because nobody wants to invest billions of tax dollars into mere maintenance.

Also, a fair bit of the infrastructure is maintained by the individual states, making any country-wide coordination of investment or fixes neigh impossible.
secureErase
"Data Science" was always a vague term, purposefully so. Useful mostly as a vendor / consultant battle-cry and hype term to "encourage" a number of new business domains to adopt digitization and automated information processing / decision support.

Various older information intensive fields (medicine, insurance, finance etc) knew the benefits and pitfals long ago. These examples show also the survival strategy for the generic "data scientist": specialization. The role of the human in the loop is to blow some context and relevance into an otherwise dead body of data. You can only do that if you really know your domain.