skysight-inc/HackerNews huggingface dataset:
> I can tell you that they wouldn't have made this kind of money on GoFundMe

Agree with you and GP. This is novel and it seems like you're rewarding someone for work instead of just giving them cash. I think ultimately NFTs will be used for this a lot more often.

> I'm no fan of NFTs as a whole

I think they're really stupid, and the carbon emissions issue bothers me, but if we can solve the environmental impact then... I don't see any harm.

I already consider the purchase of NFTs from artists (like musicians) as a kind of charity. If NFTs are kind of like a digital badge saying that you financially supported [artist/cause/organization], then I think they're great! A lot of people only give money for the status they get -- why not make it explicit and digital? I don't care what is actually in their heart as long as they give the money.
The thing is now the only way to access that linked paywalled article is to subscribe to the publication, there in no way to pay to read only that particular article.
Yes, that's like Europeans signing contracts to buy natural gas from Russia. Amazingly short-sighted.
Did you report them to the CIA?
That's one of the weirder things about running. Generally you just say "go out for a run" like there's no skill to - that's it's just effort.

Watch a kid run. You quickly realize that they have two paces - flat out sprint and walk. Pacing is something that you learn over time. The opposite extreme of that kid is someone's who's a really experienced runner - my wife for example; it's not that she's incredibly fast but she's amazingly conscious of her pace - if she wants to be consistent she'll run a mile pace that's within seconds for 10+ miles. If she's running a shorter distance she can calibrate her pace.

I think that's one of the things I like about running. The other nice thing about it - really about any form of exercise is the discipline it forces on you. Not "I go running everyday" but - I go running as often as it takes to keep me where I want to be while listening to my body to avoid injury. The more you ask of "where I want to be" the more you have to know about stopping not just going. It forces a self awareness that can be atypical.
I have had a 2XL, 4XL, and now a 5a... and the 5a looks nice but is actually a piece of crap. I can't recall EVER having a phone with this many network hiccups.
Asbestos brake pads release particles as they wear down. Asbestos in construction is just pushing problems down to the next generations who will have to deal with the stuff when renovating.

Same for PCBs, they don't degrade naturally and will persist long after the components they're in have reached EOL. They'll get taken care by the lowest bidder and disappear for decades until they surface back and become everybody's problem.

Lead is just as toxic but affects the central nervous system instead of lungs or giving you cancer.
That's the argument here, but as a defense of Google, it's a really bizarre argument. If a volunteer-run effort like LineageOS can manage to get recent AOSP Android (including all the hardware-dependent bits) running on a Pixel 3, what's Google's excuse?
Tag the link with a flag, then have the user agent refuse to load the links if it comes back with any other content type.
I would recommend Paolo Bacigalupi's The Windup Girl and other books. Violent but masterful narratives about an unhappy future.
Insightful. Would you mind talking about where you move your payment processing?
Just like the sibling comment stated. Angular does not force you to use Typescript, you can use JavaScript. Angular 2+ even used to work with Dart but they dropped it.
To add to this, especially for non-Americans or Americans unfamiliar with the tax system, the very notion of "change tax brackets" is a misnomer.

If you make $41k, you still pay 10% on your first ~$10k, 12% on the next ~$30k, and 22% only on that last $1k.

So yes, you could be in a situation where you had been at the top of a bracket, and your incremental wages from the raise are taxed at the next bracket's rate. But it doesn't trigger any kind of situation where your entire salary is now charged at the higher rate.

Yes, of course, a 5% raise does not compensate for 5% inflation. But that's just because taxes exist, not because you are entering a higher bracket per se.

IMO, the whole pervasive narrative around tax brackets being something to fear is a fear-uncertainty-and-doubt move by those seeking to vilify the tax system. It's worked surprisingly well to those ends.
Physician, Mathematician and Data Scientist: N95s Won't Work for Kids
I wonder if there are bombs that leave more radioactivity as goodbye gift, to delay the rebuilding.
It sounds like you think "tsc is slow" because "it uses shared state". If that is what you're getting at, you've connected two unconnected statements.

It does tend to imply the new tsc isn't going to be able to take much more advantage of concurrency than the current one, which may put a limit on what performance gains it can expect. I don't know if the current tsc is able to do anything concurrently. (Here, "concurrently" doesn't merely mean "able to have multiple events in flight and thus do multiple tasks at the same 'time'" but truly "doing work on multiple CPUs simultaneously".) Go is generally faster than Node, but it'll be hard to guess by how much in this case.

A Rust port would be harder but would probably lead on in a direction to improve the concurrency. However, that may be an infeasible amount of work, not because of Rust per se but because a port is intrinsically easier than a port and a rearchitecting.
https://archive.is/tpcRK for the article
You preferred Twilight? To each his own, I guess.
Infiniverse – The World's Digital Layer
Pwnkit: Local Privilege Escalation in polkit's pkexec (CVE-2021-4034)
You're right. A conservative is a contrarian. They fight change.

Chesterton's fence is a rational argument in favor of being conservative.
You mean people who can _afford_ to do it, right? Of course you do.

Well that's certainly not the majority of people, and I did say _universal_ health care, not "health care for those who can afford it".

Look, I get it... In the US, your worth as a person - and your access to essential services - is tied to your wealth.

And while that's a horrible and cruel way to be, it's all you know, so you don't see that it is, particularly if you've never been on the wanting end of that deal.
Mainframes are expensive and busy running production workloads. Offloading development and test to franken-PC's running 370 emulation had large cost saving potential. Plus, back in those days the IBM sales organization had a ton of power and could sell anything, the margins were always fantastic, and large numbers of sales reps earned more than the IBM CEO.
Spanner is in a rather unique technical position which enables it to sit outside the tradoff space of most distributed systems. You certainly pay for being robust against coordinator failure though.
Official inflation numbers are super dishonest in my opinion.
Good point. Perhaps one cheap way GP could monitor it themselves might be to just monitor pH and do a lead test if that changes.

Just replacing the pipes seems like the optimal solution, but half-measures are better than nothing.
Contracting the virus isn’t a safe way to gain immunity.
But, and this is where the equivalency annoys me. You could literally end up in jail for saying some of these things about China in China. You could just as well talked about abuses of women and the me to movement, but the reason that hasn't happened in China may well be not that there men are somehow better behaved, but that they appear to have put a women who did come out with an accusation under house arrest until she agreed to stop talking about it. Yes the US has done and doubtless continues to do bad things, part of that comes just from having power which the US has had for a long time, part of that comes from truly bad people ect. But the Snowden leak happened in the US. US newspapers reported on it. College professors talked to their class about it. You can talk about it on this US hosted and owned website. None of that is true in China, right? So yes I am more skeptical of the US doing shady business when a large percentage of US citizens object to shady business and can talk about it than I am of China doing shady stuff when they've built their internet to insulate their government from as much criticism as possible
(2) *I thought Apple had complete control over their Arm(TM) based chips as in they can do anythign they want and pay no licensing fee as long as they keep the Arm branding?
Wonderful book. There's a snippet on conflicts between engineers and how engineers approach them - often not in the best way - that I've referenced so many times in my career.
The reasoning is only strange if you assume that the cause of slowness is the shared state.

CPUs have no problems with mutability. JS is slow because of dynamic typing, dispatch, flexible object layout, and an object model that requires lots and lots of heap allocation and pointer chasing.
Insightful article but surprised at the recommendations. Teamwork is important, yes... but smaller task sizes should have been mentioned too.

>Finally, after several weeks, the engineer shares an update, and one (or many) of the following bad things transpire:

Several weeks? If you are giving developers open-ended tasks that take weeks or more to complete, imo it's asking for things to go off the rails.

The most effective way I've found to avoid this situation is to ensure that worked assigned is broken down into tasks that are as small as possible.

When assigned work is limited to small deliverables you get smaller PRs, limited business logic changes to get lost in, fewer integration changes, etc.
Maybe I should swap in the word "price increases" for inflation.

Gas prices are high now, but nobody expects them to stay at this level indefinitely. (And nobody expects the price of gas to stop increasing without then also dropping back down.) Supply-chain related price increases aren't permanent, and go in the other direction when the supply chain improves.

And the larger point is it's a positive development if workers really are able to renegotiate their compensation -- and that isn't entirely negated by slightly higher prices in January.
> It's just different use cases.

That's a hand-wavy redirection that isn't relevant to the issue at hand, which is that:

There is no evidence of the US (and, in fact, many other large countries, with exceptions for e.g. Israel) installing backdoors and breaking into computers in order to steal intellectual property.

There is ample evidence of China doing exactly that, against a variety of targets (not just the US - they've taken things from Japan and the EU, among many others).

I wouldn't be surprised if every nation with a functioning Internet connection tries to put the hac on whatever they can.

But that's not the topic under discussions - the topic is stealing and commercializing IP, for which there is tons of evidence for China doing, and accusations of e.g. the Five-Eyes doing it are rampant speculation with absolutely no evidence included.

Yes, that includes your comment.
Out of curiosity, how often do you have a project in the first mode that gets large enough that the speed of compiling TS to JS is significant?
Hey sorry, I'm late to the game -- I didn't realize you responded. I do understand your view completely, and maybe I came in reactionary. Honestly I'd have to continue thinking about it to provide any sort of meaningful answer -- but I will definitely continue to consider it in any thoughts or comments I make in the future, haha.
PostgreSQL has excellent JSON support today, including advanced queries, indexing, constraints. There are many cheap/free managed offerings that could rival SQLite in operational simplicity.

If you want a SQL interface to JSON with room to grow, that's your best bet IMO.
It looks like that isn't available for those in the US, since the redirect takes me to a 'not available' page. Are the 'Signature Edition' versions at all available in the US?
And yet, today I'm one of the 10000: https://xkcd.com/1053/
Many years ago one of the lispers wrote on Usenet that: "So I can't really go into many specifics about what happened at Google because of confidentiality, but the upshot was this: I saw, pretty much for the first time in my life, people being as productive and more in other languages as I was in Lisp. What's more, once I got knocked off my high horse (they had to knock me more than once — if anyone from Google is reading this, I'm sorry) and actually bothered to really study some of these other languges I found myself suddenly becoming more productive in other languages than I was in Lisp. For example, my language of choice for doing Web development now is Python."

One should consider that home offices are great compared to average offices, but they may or may not be great compared to the best offices.
Google's phones aren't locked - they're already 'jailbroken' when they're new. What would that regulation accomplish here?
> invoking so-and-so's law or this fence isn't a productive tactic.

Not true. If we both are familiar with the concept, saying "Consider Chesterson's fence" conveys a lot of information. If we aren't, chasing down the reference will almost always result in a much more articulate version of the concept than whatever you or I would come up with on the fly.
I cannot figure out why the US writes laws in terms of nominal value while maintaining an inflationary currency. The majority of lawmakers agree that a law should be x with respect to the current value of USD, why don't they also agree it should be x+inflation for a future value of USD? Maybe with a circuit breaker for hyperinflation. They don't have to rely on third party inflation numbers, because the Fed is a government agency.

Do some lawmakers only support a law because it will have a lower (min. wage) or higher (tax) real monetary significance in the future?
This is my guess. They're worried about precedent. If this is allowed to stand it gives other jurisdictions a roadmap for how to shut this down
A better option is to use Cell or RefCell; they allow completely safe shared mutability in single-threaded code.

https://doc.rust-lang.org/std/cell/
Yeah your first approach to runtime dispatch is just dumb (don't listen to those silly people), you want the second in all cases, even with a closure implementation of classes. Objects should be implemented as in the second case, or more concretely, as:

struct MyObj {
vtable: MyInterface*
data: void*
}

Which is how dynamic traits are implemented in Rust. The C++ approach of a pointer to:

struct Obj {
vtable: ...
field1: T1
field2: T2
field3: T3
}

Pretty much means you need to define all the interfaces you implemente on class declaration, which is not nearly as nice as doing it independently (as with traits, protocols, typeclasses, go interfaces, etc.)

My point is that MyInterface is just a vtable, a class is a function that fills in that vtable, an object is a pair of a filled in vtable and data. These mechanism are restricted to the compiler for no good reason, which is why you end up with "metaclasses" and "mixins" and all that other nonsense. Just expose the mechanism itself and give it some nice syntax.

Classes mix too much stuff together: inheritance, subtyping, access control, data specifications, interface specifications, etc. We've figured out that's not really a good thing which is why Go and Rust rightfully split them up and use separate mechanisms.

I'm saying go even further and don't hide the runtime representation, let me create these things at runtime if I so wish. That gives metaclasses and mixins and what not for free (with a constexpr-like mechanism they can even be done at compile time).

You can still keep traits as the way of defining bundles of methods, they're also useful as generic concepts, that goes into the ergonomics of it.

This is a similar discussion to Zig generics. Zig has no idea what generics are, a "generic" is just a function that given a type produces another type. Works pretty well.

> A class is any construct that can:

That's just your definition. Your points describe an abstract datatype, a concept that predates classes. We could call that a class these days, but that's not reflective of the programming language construct called "class" as used in language like C++, Java, C# and friends.
I mean.. that's not a feature. That's a bug (likely due to RAM being full). I rarely if ever have this issue, but I do remember it happening at some point, but that's definitely not a feature that iOS thinks is better.
Germany is refusing to help protect Ukraine because its industry is completely dependent on Russian energy, not because of some lingering WWII guilt.
I don't really get the point of Deno anymore. First they were all about their sandbox/security system, but since you couldn't specify that per module it turned out basically useless.

Then they had "url" imports, but now they're adding npm compatibility. At that point people will just keep publishing on npm, so I don't see why I should go to the trouble of switching to Deno.
My Windows machine is something like 5 years old. Microsoft will keep supporting it until 2025 and even by then I will probably have switched it to Windows 11.

Smartphones go unsupported after a few years? Why do we put up with this?
I think there's kind of a tacit understanding with business owners and legislators that if you collect taxes, you're good. Bezos and Musk might not pay taxes personally, but they oversee operations that result in payments of sales taxes, payroll taxes, employee income taxes, property taxes, etc, in vast amounts.

The historical critiques of class warfare have some good points, because there's obviously a privileged class here that's doing really well on the backs of labor, and this privileged class can afford to buy (and let's face it, it's really bribe) itself ever more privileges for a very tiny share of their wealth.
(EdgeDB CTO here)

> The schema you have designed helps a lot on the server-side. If this schema can be extensible (that is, people can make extensions by allowing extra information in the schema that the DBMS ignores, similar to comments) and available to an authorized user, people can create great tools for the client-side as well.

EdgeDB supports arbitrary JSON annotations on all schema objects, for example:

type User {
property name -> str {
annotation render_as := '"textbox"';

constraint expression on (len(.name) < 10) {
annotation comment := '"needed for external reasons"';
}
}

annotation data_for_app := "some-json-data"
}

> I'm throwing away Prisma integration of my company's project because they did not provide enough extension points, hooks and all the other ways to use the full power of the database. So as soon as you need something they don't support, you have to bypass the whole abstraction layer.

This is why we are investing so hard into EdgeQL. If you can't express something with EdgeQL that you can with SQL -- it's a bug. If whatever you do seems _harder_ (or slower) with EdgeQL than with SQL, it's also a bug. Same applies to generated database clients (we'll be releasing a JavaScript/TypeScript client generator / query builder alongside EdgeDB 1.0).
There is a huge difference even in small and mid-size projects.

https://datastation.multiprocess.io/blog/2021-11-13-benchmar...
Where I work everyone will do their check-in but the important part is that everyone has a different personality. Like some people can be more confused and have a hard time explaining or even remembering what they did before so it's helpful to ask questions during their check-in to see if they need help. Some people might work on the same task for weeks. People are often afraid to ask for help. Or, maybe their task needs to be broken into something smaller given new information. The daily check-in is also a way for them to connect with someone else in the team who can actually help them. I'll tell them to either hang out at the end of standup or schedule a meeting with each other.

Having someone leading the standup, if done correctly, can help hold people more accountable for what their progress is toward the sprint goal and remove obstacles. This is one of the responsibilities of a scrum master although you don't need to be a scrum master at all to do this.
It always felt a bit off to use the label "natural immunity" for a virus that many (especially whose who use this label) believe to have originated in a lab.
The company spent US $5 billion (about $40 billion today) to develop the System/360.

From this article, which describes the development of S/360 in detail: https://spectrum.ieee.org/building-the-system360-mainframe-n...
I'm really curious to see how the func/proc distinction will work in practice because I'm all for that funcs are side-effect free to the caller but the fact that they have to be a single expression feels like it would bifrucate the style of any project into functional and procedural to the dismay of someone reading your code in the future.

The fact that I can't take something in a proc block, remove the side effects, and shove it into a func feels like effort for its own sake and makes it more difficult to use funcs when you want to maximize their use for the mental load of the caller.
The main problem is SoC lock-ins.
You can find aftermarket AOSP for Android devices.

Sadly it's inferior of the days where you can run a mainline OS on 20 year old device (eg. it is possible to run 32bit Windows 10 on first Intel MacBook from 2006).

Another thing is apps, usually us developers drop "legacy" OSes as it's hard to support them (or worse a mobile store enforces dropping such support). So someone with old phone can't even use it anymore.

There are some "open-source" SoC or more environmental/reusable approaches but it's just a drop in the ocean.
Where's the part where the US steals and then commercializes Chinese IP?
https://deno.land/benchmarks is what you are looking for.
One of my favorite quotes on the topic:

"Shaq is rich. The white man that signs his check, is wealthy." [Chris Rock]
Blue Bubbles vs. Green Bubbles – The iMessage Lock-In [video]
Sam Altman Cofounds Worldcoin, Now Valued at $1B
>Eating mummies is also completely different from literally killing someone for the purpose of eating them...

Europeans did both. Everything I stated is factual and didnt require alteration or retraction. You on the other hand, have been proven wrong over and over again and that anecdata from a wikipedia page as a source is laughable.

Re-read the thread and quotes, perhaps you missed the part where you lost this argument. We need to argue using facts and citations, not feelings. You, for one, being off by 2-3 centuries is not trivial in a discussion of recent history.
That is not what I meant, but also pretty interesting.

I actually mean the 'definition' of the syncs themselves.

I am picturing JSON or YAML that describes the source fields, their mapping to the destination fields, and any other meta about the sync: frequency, number of retries, whatever else that you could configure in the UI

So when I go and update my dbt model to modify one of the tables that I am syncing from, I can make the corresponding changes to my Castled settings file, and release it all as one atomic update to my data infrastructure.

It might be a small number of people who would want something like that, but it's definitely something I would have been excited about when I was running a data team.
I'll be honest - half the time it's trying to keep it from other engineers who are overly eager to have an opinion because a) they're low-output and looking to posture, and/or b) or want things to be done a different way.

At least the business side of the house appreciates the spec'd work being accomplished.