skysight-inc/HackerNews huggingface dataset:
Life is harder immigration-wise in the US. Even if you have a clear pathway in your mind and a relatively (surprisingly?) short timeline for getting PR, things might just not be that smooth - and I believe I speak for many of us who have been through that in the US. A green card process alone, assuming all priority dates current and everything in check, takes about 2 years, let alone the wait time for you to be even eligible for that. It's not that simple. Plus, you can only bring your parents if you're a US citizen, so add 5 years to the 2 years expectation, and their processing time as well. Altogether, we're talking about 10 years for that to happen.

The US has amazing opportunities career-wise, though. Obviously, it pays much more than Canada or any country in Europe considering the same job level.

Healthcare might also not be "better and faster" or houses "cheaper" than Canada. You excluded SF and NYC but then proceeded to compare with Toronto, which would be the "equivalent" of these two cities in Canada. So that's not a fair comparison. Prices are very much bloated in the US. Everything costs a lot of money so you also make a lot.

All in all, it really depends on what you want for your life. Which country do you identify the most in terms of their values (yes, that's a real thing)? Have you met Americans and Canadians? People play a large role in how your life is gonna be day-to-day, so you might benefit from such a perspective. You can probably make money in any first-world country in the world and have more or less the same things (a roof over your head, health, education, quality food).

You'll most certainly have more disposable income at the end of the month in the US.
Hmm, I believe it does. Not in all cases, but in a substantial number of them.

I can use cash to buy groceries or a soda at the corner store each day, and while I suppose I'm not entirely anonymous to those parties I may as well be. The grocery store is certainly reporting my cash transaction to the appropriate authorities.

Sure, this doesn't apply for all use cases. However, it applies for a lot of things that currently are tracked by using electronic forms of payment. These spending patterns were simply not tracked on an individual basis until the advent of the shopping club cards, which eventually became redundant due to the use of electronic forms of payment.

The level of tracking from "I take out $400 in cash every payday from the ATM" vs. "I spend it in $10 increments on the following items" is wildy more invasive.
I read it the same way you did, but I'm confused that paying out insurance gives the insurer a stronger claim to property than buying something. Is a wreck at the bottom of the sea only still someone's property if that someone is an insurer?
The parent was talking about the UK, while your link is for the US?
You can find thousands of videos on YouTube showing things people do with iPads. You can watch those videos on the iPad.
SPA's need not be complex nowadays. I use https://lit.dev 's templating engine. When I want something simple, I use just the templating engine not the full web component framework.

Lit's templating engine is just html that is made super efficient to render because only parts that change are re-rendered. There is no inter language to learn like JSX. It uses native browser html parser, native browser templating capabilities (<template> tag), native event handling and native literal template capabilities of javascript.

I have a simple wrapper class that renders and composes components efficiently and reactively when state changes. The views look like:

class TestView extends LittleLit {
static get properties() {
return {
paramter: {}
};
}
constructor(){
super();
this.el=document.querySelector('#main');//root component attached to the dom

this.subcomponent=new SomeView();
}
render(){
this.subcomponent.somestate=this.somestate;//propagate state down if necessary.

let h=html`<H1>Hellow ${parameter}</H1>${subcomponent.el}`;
render(h, this.el,{host:this});
}
}

To use

v=new TestView();

v.parameter='world';//this triggers rendering if the parameter changed.

Here is my whole framework:

class LittleLit {
constructor() {
this.el=document.createElement("div");
this.refreshScheduled=false;
this._properties={};

let properties =this.constructor.properties;
if(properties!==undefined){
for (let prop in properties) {
this.property(prop,properties[prop]);
}
}
}
refresh(){ //you can call refresh to trigger rendering efficiently
if(this.refreshScheduled===false){
this.refreshScheduled=true;
window.queueMicrotask(()=>this._update());//deduplicated rendering in an efficiently scheduled microtask
}
}
_update(){
this.render();
this.refreshScheduled=false;
}
property(name,options){
Object.defineProperty(this, name, {
set(v){
if(this._properties!==v){ //refresh only if property changed
this._properties[name]=v;
this.refresh();
}
},
get(){return this._properties[name];}
});
}

}

Most of the power comes from the templating library: https://lit.dev/docs/templates/overview/
Hi, new grad / junior developer reading this. Where do we learn this stuff if we don't already have a job?
Do you have any data on the reliability of OCR systems used in production? I don’t have any such data, but given that the USPS was using OCR to sort mail over 50 years ago I would be surprised if these systems aren’t incredibly accurate.
Please stop creating accounts to post unsubstantive comments and flamebait. It destroys what this place is supposed to be for, and will eventually get your main account banned as well.

If you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules when posting here, we'd appreciate it.
> Given the JS ecosystem cycle, React will be replaced by something better much sooner.

The JS ecosystem cycle has slowed way down. React is 9 years old now. Vue is 8 years old. Svelte, the new kid on the block, is 5 years old.

If React is halfway dead, and I doubt that given how much $$ is being invested in new React apps today, then that is still another 9 years of React.

I do agree that Meta will be around for longer than 9 years though! :)

The other thing people don't realize is that React Native is huge. It has been ported all over the place, the basic idea of "universal UI primitives that you write native backings for" is a pretty good one, and JSX is a really nice templating language.

I'm not a fan of quite a few things about React, but its design is solid enough that it isn't going anywhere.
My experience in Japan is they are very bureaucratic. It's actually amazing they have progressed this much. They are also very patient, people use cash and they will count the coins in their own pace in a long line grocery cashier and you won't see any one complain.
What are they going to do about that 10s of thousands of Starlink satellites that will start interfering with observations?
The key to doing this experiment well is having the right facilitator that brings the attitude. A good facilitator will roleplay a leader/manager/exec that will praise when measures are good and berate when measures are bad. The idea of this experiment is to show how management can harm the process even when there is inherent variability, good or bad.

Here is Dr. Deming himself performing the experiment
https://www.youtube.com/watch?v=7pXu0qxtWPg
Yeah, Meta will probably die like AOL, which is fitting since (at least in a rhetorical sense) it's also mostly lived like AOL.
That was a very readable comment. I'm reminded of the times I've posted here about "If it's 3 paragraphs or longer, my coworkers won't read it" only to get responses like "Must be poor writing on your part!"

I wish to thank you for proving my case.
I think you will find that countries with a bread culture (e.g. Switzerland, Germany, France, etc) will not agree that what you consider bread is what they consider bread. This is a question about quality, not labour prices.

Take the inverse: in Germany, by and large, a hamburger is that thing you get at McDonalds. That Americans typically pay more than $2.00 for a hamburger is not a sign of high labour costs, but rather that they'll buy something better instead.
Rails and Ruby bake in a lot of really nice, ergonomic features for every day programming, not just larger architectural decisions. For instance I am working on a React Native app in my spare time and so much of Javascript seems tedious. Example is dealing with date ranges.

Contrived example:

import { isWithinInterval, subDays, addDays } from 'date-fns';

const today = new Date();

let range = {
start: subDays(today, 1),
end: addDays(today, 1)
}

isWithinInterval(today, range)

The functions for this kind of calculation has to be imported into any file I want to use them? There seems like a lot of copy pasting of this kind of stuff everywhere in a robust javascript app. I think it's reasonably easy to read and understand, so I don't fault that, it just seems tedious to use tons of libraries that you have to explicitly import everywhere to accomplish simple things. Feels like death by a thousand cuts.

Meanwhile in Ruby (with Rails) this is functionally equivalent and is usable everywhere in the code:

Range.new(Date.yesterday, Date.tomorrow).include?(Date.today)

edit: fixed some bugs :)
You pretty much always have to make sure that everybody associates the same meaning with words. In politics this is often used to be deceptive. Somebody who says he is a “socialist” may mean something different than what some people are hearing.
Very good initiative and I think that Australia won't have any problems with dark skies, considering how sparsely populated most of the continent is. Have a look at these dark skies maps:

https://darksitefinder.com/maps/world.html

https://www.lightpollutionmap.info

https://www.cleardarksky.com/maps/lp/large_light_pollution_m...
Recursive toy NFT of Twitter profile pictures
And over the last 40 years has slowly consolidated back again.
I wouldn't describe the presentation as idiotic but it was hard to take seriously. The dream of immersive VR experiences showcased in Snow Crash and Ready Player One will be realized.

But it won't be soon, and the ideas shown in the video--like the surfing game--were the kind of ideas that litter the floor of the App Store.

Compelling product experiences, especially on new platforms, are extremely difficult to craft.

The taste of the creators must be exceptionally good and in this case the hardware quality and onboarding experience must bowl over anyone who touches it.

The Facebook video for Meta looked very speculative. I suspect Meta was planned for 2023 or 2024, but was rushed out the door because the brand was getting pummeled.

In that way, changing to Meta was very effective at derailing the negative attention. But not actually having a there, there is a problem when the chicken comes home to roost.
Yep. My partner and I have had the same thoughts about having a property outside of the city that's large enough to entertain in. We jokingly call it The Compound - but there is something to the name I think in terms of how it needs to be designed to fulfill that need.

At a bare minimum it needs to be large enough to have a guest suite - the central socializing spaces like the kitchen and living room also need to be scaled for that use.

Ideally (assuming a grand budget) you can have separate structures for guests entirely.

But certainly one has to assume that guests are bunking over, given how remote the location is. It seems eminently unreasonable to assume guests are driving several hours at the end of the evening.
"hey welcome to your first day at Amazon! We're so excited to have you. Here's your desk, and here's your PIP. Oh yeah, here's your computer too"
Maybe I'm not following the thread (I'm not sure what "In what concerns .NET is wasn't really better" means), but what's the issue here? C#'s fastest framework beats Go's fastest by a marginal amount (60.1% vs 59.1%). That's probably within the error margin. Anyway, drawing sweeping performance conclusions from microbenchmarks is perilous--a high ceiling for an HTTP framework doesn't indicate anything about real-world performance for web applications (which are almost never bottlenecked on the HTTP framework).
> A slow death on the order of 10-20 years may happen

A sibling comment even said,

> Meta's death (if it happened), will be a slow and a long one. Like Oracle or IBM (although IBM is not completely dead).

I think death could happen a lot sooner. Rapidly, even.

Meta is not B2B, but B2C. They won't have ten year contracts, legacy workloads that they can raise costs on, or new businesses to schmooze over a game of golfing with the execs.

Social is fickle. MySpace and Digg died in an afternoon. All of the centuries of dead and forgotten stored content isn't keeping people there. It's connections. And those can come and go easily. Just look at Snapchat and TikTok.

Meta employee compensation is going to begin decreasing both in terms of salary and stock equity. They won't be able to retain good talent, so initiatives will die. Meta is also in a narrative death spiral, and this will eat away at employee morale.

New startups will see blood in the water. They'll come after the Baby Boomers. They'll come after the photographers. Facebook won't have capital to fight battles from every angle.

They have a massive amount of infrastructure to maintain. This will become a giant thorn if they lose employees. How will they weigh keeping the lights on, finishing ongoing migrations, etc. vs fighting new battles to stay alive?

We now realize how little moat they actually have. Facebook really needed a device. They tried to build a handset and failed. Oculus is too little too late.

edit: Facebook ads will cost a lot less as advertisers demand more favorable rates and see diminishing value, perhaps even abandoning the platform for their ad spend.
That's sad because it means there was no evolution in the last 20 years. People learn something, teach it and it gets frozen. Nothing new is learnt for decades.
This is already getting coverage in Russian media.

Your assumption that our politicians need a lot of influencing to care about this is probably wrong, especially since these leaks lead to financial losses.

I'd be more surprised if the US did something about it than Russia, to be honest.
If I could steal 325 million dollars and get away with it I would.
I'd say it is probably because we are all worst at writing code than we'd like to imagine. So writing necessarily complex code, especially in a FOSS compiler or system, makes little sense since some day someone else is going to have to step in and learn it.
Just to note that the exemptions on this are quite easy to get.

Right now, you only have to spend £3500. If it costs more than that to get to the required EPC rating, you can get an exemption. There is also the "seven year payback test", which is as it sounds.

What this means is yes, this may drive your landlord to install LED bulbs and thermostatic radiator valves, and maybe some double glazed windows, but it's not going to trigger a mass drive towards modern insulation and solar panels.

Personally I think we should just force landlords to bear the cost of heating to 18c.
A better template library would be a killer feature. Similar to what PHP has been since forever; the ability to write HTML using all the Go language's features.
Interesting reference point because I've heard AOL has continued to be a cash cow for decades: https://www.statista.com/statistics/266568/annual-revenue-of...

Advertising revenue is obviously more fragile, but I don't think Facebook cresting the high water mark says all that much about the tail trajectory.
Branch prediction is a CPU "complexity" that got us in to some amount of trouble.

I don't see simplicity as a "virtue", as such: it's all about the ability to reason about a system. The more complex it is, the harder this becomes. This makes it harder for implementers to work on it, and harder for users to figure out what is going wrong.

On the other hand, complexity often offers useful enhancements such as features or performance. There is some amount of tension here, which is hardly unique to software: you see this in, say, tax systems, regulation/law, design of cars and all sort of things, etc.
I still haven't gotten over the transition from init to systemd. One reason is that I'm unconvinced it makes sense to have a daemon that passes out root privileges after boot. I'm a fan of "keep it simple," and UNIX/Linux/BSD survived for decades without such a daemon.
Querying GitHub Data with SQL
Yea, the way they turned the bleak situation into something sanguine is fascinating. I still remember how expensive is MRI. I used to earn like $150 usd and the cost was around $200 usd. I hope such inequality shall perish in the future, so people can at least get proper treatment.
Mid 40's here. I have a single friend that still posts frequently. Everyone else has either dropped off entirely or rarely posts. My wife is on facebook all the time, but it's for her social groups, like Mom, teacher groups.

At least for me, the overheated political posts became a huge turn off. I think many people left after the election.
Yes, but context is key.

Denoising can on average improve the result, but sometimes it will be wrong.

Spotting when it goes wrong is potentially a difficult task, but generally the difficulty scales pretty clearly with the difficulty of understanding the original image anyway. If you can't spot when a denoising filter has screwed up, chances are you wouldn't have spotted anything interesting in the original image anyway.

But once an AI is context-aware things get way more complicated - it will try very hard to produce an image that doesn't _look_ wrong. Even if it goes wrong, it can go wrong and still succeed in managing to make an image that looks correct, it just no longer matches the real brain that was scanned. Perhaps it decided a tumor was just a smudge on the lense, and invented some brain to go behind it. An operator expecting to see brain and seeing brain wont think anything of it. When the patient dies, they may look back and say "wow, that tumor didn't exist at all just 3 days before! that should be impossible!".

tldr: Having an ai that might make mistakes is one thing, having an ai that can just invent exactly the data everyone is expecting to see is dangerous.
I'm sure that's what MySpace investors thought.
They could (and probably should consider) going the Ionic route and building some generic layer that allows them to integrate with Angular, Vue, and future frontend frameworks.
And SQLite is "basically" doing what Hadoop does.

Except not really, because one is architecturally simple and relatively easy to grok/hack, and the other is big and complex and built specifically for operating at a massive scale and multi-team environment.

We're talking ~200 combined LOC of idiomatic Go+TS & a couple popular libraries vs. an entire SPA framework and its various DSLs.

State synchronization over a long distance is always going to be a balancing act of performance vs. reliability vs. security. It's never simple and outsourcing those decisions to a framework is not always the correct choice as it may bite you later.
You haven't explained why you think they shouldn't "feel like anything". How do you distinguish "feeling like anything" from anything else you experience?
Thanks for sharing op. It's interesting how this result would in some ways align astrology theory more closely with the tarot. For example in the sense that a reading serves as a semi-random source of contextual perspectives to consider. Similar to Brian Eno's Oblique Strategies.

Personally I tested out various astrology services and sources recently, paid and unpaid, and learned a lot I didn't expect. For example I found that an unexpected highlight for me was the advice taken in isolation. For example, "generally when X happens, it can help to try Y or Z," which in many cases was new to me and not obvious, but helpful.

I also found entire subjects which taken into consideration were fascinating. Like astrocartography. The invitation to think more intentionally about places of dwelling and the sheer variety of effects on the subject was pretty cool.

On the negative side, I paid for one report that was just terrible for a newcomer. Gobs of advice overlapping and contradicting on multiple timelines. It was computer-generated so I didn't expect the subjective quality to be great, but trying to read the report was actually more frustrating than just reading snippets of randomized advice.

I also learned that predictive ability was (surprisingly to me) not really advanced by professional astrologers anymore, taken as a group. I was reading through some conference proceedings and there were a lot of interesting things said about this.

They might say, "it could be that X happens" but the intent is often to communicate that it's an idea to weigh and consider rather than believe. Tarot and cleromancy practitioners were similar here too.

One practitioner even said that humans gained the ability to think and act for themselves fully something like 200 years ago (?) so this predictive stuff wasn't worth much anymore.

Overall it's a pretty fascinating world with a surprising variety of beliefs and practices.

(Also just learning that cleromancy is a thing was pretty fun...)
Are your AAAA records misconfigured?

$ dig +short antonok.com aaaa @phoenix.ns.cloudflare.com
fe80::216:3eff:fea9:4e8f
From: https://research.aimultiple.com/ocr-technology/

"There are still no OCR tools that work at human level in most applications"

and also from my personal experience working with this technology every day. There are many more mistakes in OCR even with printed material than might be expected.

There is a major problem with Xerox Scanners and the 8's and 0's issue I reference.
If Meta dies the economy will follow. Meta isnt going anywhere. If Oracle is employees massive amount of people Meta will for a long time to come. Look past one quarters earning reports.
I'm kind of thinking the opposite. Image analysis is where you don't want AI. Noise removal is further upstream (I'm assuming) and if it fails wouldn't it cause significant artifacts (blur for example) in the images?

It would be helpful to see results with and without this correction, or even with varying degrees of it.
Could this be an alternative to Elon’s neural link? Is it wearable?
There was a lady in one of my previous projects whose job was to maintain the integrity of sensitive financial data (she was doing a lot by hand, as they wanted a human to check every number). In the 2 years or so I worked there, there was not a single mistake from her. I didn't hear much appreciation for her from others, but my CTO used to call her the most important person in the company.

Some tools, some people just work, just do their job quietly and efficiently. They do not get any appreciation, precisely because they are too efficient and go unnoticed. JS is not one of them for sure.
Maybe. But they can also afford to wait.
Yeah, power always consolidates unless people use violence (or threat of violence) to stop it. Companies merges to bigger companies, company owners loves this, that is bad and gives people less freedom. Countries merges to bigger countries, politicians loves this, that is equally bad. The more the power is spread around the better, but everyone who sits on power tries to work against that.

Note that giving all the power currently held by capitalists to politicians is also consolidation of power, that is bad. Or vice versa. So giving the government too much power over companies will hurt on the other end, balance is needed and it is hard to say where the line should be drawn.
The guy that forgets to turn a light off is pretty irrelevant, but you can look downtown in my city and see countless office buildings with all the lights on 24/7. They're literally keeping me up at night with the light that's shining in my windows. It would be relatively easy to create and enforce a rule for the largest wastes.