skysight-inc/HackerNews huggingface dataset:
I started learning in my late 20s. Am 36 now, and feel on top of my game. As in, I'm familiar with what tools are available, and am able to apply them to solve practical problems in several domains. I have never been able to do something well on the first few times, nor could I pass a coding interview, I speculate. Those might be more age dependent. But, through iterating, careful documentation, and choosing or writing clean APIs, I feel well-equipped. Some new tools really help - Rust in particular. And Vulkan, modern JS/CSS, modern ARM MCUs etc.

I do feel... somewhat disconnected. Ie, my thoughts on what a good API or lib looks like is different from what I find most often in the OSS world. Not sure if that's age-related. I re-invent wheels.
WebKit was forked from KHTML by huge company that employed people to work on it. And was later forked again into Blink by another huge company that employs people to work on it.
I didn't mean to imply Kant was the sinner, just that his words are
heretical today. When he was saying it, it was to the applause of his
peers in the spirit of that age.

Try criticising the moral supremacy of rational prediction (for
example algorithmic policing) now, and they'll nail you to tree and
set it on fire.
okay I will be that guy.

funny how it comes right after major rouse because of their ethically murky use of open source code.
That's quite a price difference, I have the first gen Roost and I paid £60-70 if memory serves.

The new Roost v3 looks sturdier while the Nextstand looks like my OG Roost, which I note they've now discontinued looking at their site.
Wikimedia Foundation | Remote Worldwide | Full-time
The Wikimedia Foundation, the nonprofit organization that operates Wikipedia and the other Wikimedia free knowledge projects is hiring several fully remote positions.

- Staff Site Reliability Engineer: https://grnh.se/d387b68e1us

- Database Administrator: https://grnh.se/7af2c7c61us

- Senior Manager, Site Reliability Engineering: https://grnh.se/00f271c81us

- Senior Site Reliability Engineer - Platform: https://grnh.se/1c9a21281us

- Senior Software Engineer - Growth: https://grnh.se/898cc11e1us

- Senior Software Engineer - Metrics Platform: https://grnh.se/2b9a95a11us

- Senior Software Engineer - Performance: https://grnh.se/be960c301us

- Senior Software Engineer - Structured Data: https://grnh.se/c06662ee1us

- Senior Software Engineer - Wikimedia Enterprise: https://grnh.se/1290aca81us

- Software Engineer: https://grnh.se/35f9053d1us

- Staff Systems Architect: https://grnh.se/f78eb2d11us

- Staff Software Engineer - API Platform: https://grnh.se/dc0341f21us

- Director of Product Security: https://grnh.se/5f4586e21us

- Data Engineer: https://grnh.se/277eb2aa1us
There was a time when investors/the board could fire a CEO making terrible decisions (like sinking billions into white whale VR projects), but no longer.
In no way. The DDR was a communist cesspit of a proxy state for the USSR from day one.

It was not socialist. It just called itself that.
Marco’s Rule of Software Stacks (Expanded)
LiveView's growing pains were definitely pretty bad (the early days of it had some pretty obnoxious breaking changes), and I can see while still disagreeing about the magic comment, but what's wrong with Elixir's docs? They are, hands-down, the best language docs I've ever interacted with, and that very much includes C#, so I'm a little baffled as to where that complaint comes from.
> And that PC's functionality is dependent upon code contributed by dozens of large technology companies. Even GCC and Clang work well because Intel and AMD contribute to them.

That really doesn't seem like the same problem; there's a world of difference between being wholly at the mercy of one company (Facebook, Microsoft, Apple) vs "dozens of large technology companies". If tomorrow Microsoft disappeared or turned more evil, Windows users would have a problem. If tomorrow Redhat disappeared or turned more evil, Linux users at large would be totally fine, and even folks in the RH ecosystem would recover quickly enough (probably by rebasing Rocky directly from Fedora).
Does it matter as long as he is the cause of them getting compensated?

Vengence isn't the same as justice. If you care more about zuck personally hurting than laid off employees being compensated, you are after the former not the latter.

To use the car accideny analogy - do you also think its a cop out for people to have insurance?
What do you mean by "all sellers"? Does that include people selling used devices?
It doesn’t seem clear that ‘an expensive looking bar and VIP room’ will always generate more profit then speaker floors.
I've been using Thunderbird for both work email and personal email (via Protonmail Bridge) for a few years now. I'm really stoked to see it's getting the attention it deserves.
Yes, you're missing out. Rebasing isn't about reducing the number of items in history, although it can do that too. It's about having a sane, readable history.

If you write two commits in your local feature branch, then pull master in and generate an ugly merge commit, and then stack two more commits on top to your local feature branch, and then finally get all that mess merged to master, you have a difficult to read history because of the merge commit randomly in the middle. Whereas if you instead rebase onto origin/master (after fetching of course), you get a nice history where your feature branch commits are cleanly on top of origin/master, so there's no crazy merge commits in the middle.

Most people just use git as a fancy save button, and therefore never actually use the git log / git blame to answer questions about why some part of the codebase is the way it is, and therefore they never realize why their merge commit insanity is so destructive to the usability of the git log.
For a 1 man team there is no point. Even for a 1 man team with a local and remote repo there is no point, because your local branch is always the same as the remote branch.

For a 2+ man team that does not protect the remote repo (i.e., don't require merge/pull requests, and you can commit/push directly into remote branches), then there is no point because... When you go to push a branch and remote complains about changes existing on remote, so you must pull first. You issue a pull and that does a fetch/merge into your local (commits are overlaid in order by date committed - some people complain about this and is why they rebase (commits from remote are back filled, and then your commits are inserted)).

For a 2+ man team that does protect the remote repo, and does require merge/pull requests then an explicit rebase or merge is needed, sometimes. At the end of the day you should be creating a merge/pull request from a source branch that has all of the changes as the remote target (at that point in time) to help the reviewer/approval only see your changes. If you updated your local branch via a rebase then the commits related to your changes are all in order, if you updated your local branch via a merge then the commits related to your changes are interlaid between other commits that happened around the same date). But really that's only a problem if someone cares to use git-log and not the 100 other ways to review history.
15 year fixed rate mortgages are always lower than 30 year fixed rate, at least in the US.
Interesting lead. Thank you.
There's always this, as well -

"On 6 December 2021, approximately a hundred Rohingya refugees launched a $150 billion lawsuit against Facebook, alleging that it did not do enough to prevent the proliferation of anti-Rohingya hate speech because it was interested in prioritizing engagement."

https://en.wikipedia.org/wiki/Facebook_content_management_co...
One great example of this was back in the P4 era where Intel hit higher clock speeds at the expense of much higher latency. If you made a binary for just that processor a smart compiler could use the usual tricks to hit very good performance, but that came at the expense of other processors and/or compatibility (one appeal to the AMD Athlon & especially Opteron was that you could just run the same binary faster without caring about any of that[1]). A smart JIT could smooth that considerably but at the time the memory & time constraints were a challenge.

1. The usual caveats about benchmarking what you care about apply, of course. The mix of webish things I worked on and scientists I supported followed this pattern, YMMV.
AFAICT from people I know it's a mix
Yes, it's a well solved problem and much easier to do in Python. The author just wanted to do it in Rust, that's all.
That doesn't make any sense. You decide what they read. You would want to know if it's harming their mental state. Closing your eyes to the impact you have does not negate the impact
Taking notes, thanks :)
Correct! By law, they're required to give it to you. If they refuse, just use an app on your smartphone. (eyemeasure is the one i used)
Oftentimes the people who say this have never done modern frontend development (and many times no frontend development at all!).
Great idea. So you have hands wide apart and canted outwards?
Including fiction (but excluding the scihub mirror, and comics), Libgen is actually about ~60TB. Z-Library mirrors this, and adds about ~24TB exclusive to them.
who should be the CEO is besides the point, certainly many more talented and driven people out there
> Anyone know of a configuration option or something somewhere that I can enable this?

I'd suggest that you retrain yourself instead. "HEAD" and "head" are not the same thing, and any fakeout configuration to change that will also be nonstandard and not available everywhere.

The underlying issue is that HEAD is the label Git uses for the reference to the top of the repo. It's saved in the filesystem as .git/HEAD.

MacOS filesystems are case-preserving by default. Linux/POSIX filesystems are case-sensitive by default. I consider this a bad default setting in macOS. Try "cp FILENAME filename" sometime. :(

Anyway, consequently, on default macOS, "head" will be remapped to "HEAD", if "head" does not exist. Watch out for "Head" and "hEaD" though. Of course those won't happen in normal Git usage (though they could be valid, and different, tag names!).

My suggestion is to not let bad macOS defaults creep into your habits. And to not make things even more weird by trying to reproduce their bad behaviour in non-macOS environments.
Something that fascinates me about this kind of A -> A translation (which I associate with the original HP Dynamo project on HPPA CPUs) is that it was able to effectively yield the performance effect of one or two increased levels of -O optimization flag.

Right now it's fairly common in software development to have a debug build and a release build with potentially different optimisation levels. So that's two builds to manage - if we could build with lower optimisation and still effectively run at higher levels then that's a whole load of build/test simplification.

Moreover, debugging optimised binaries is fiddly due to information that's discarded. Having the original, unoptimised, version available at all times would give back the fidelity when required (e.g. debugging problems in the field).

Java effectively lives in this world already as it can use high optimisation and then fall back to interpreted mode when debugging is needed. I wish we could have this for C/C++ and other native languages.
Right - they had a beautiful campus and thousands of highly-paid employees. Add in all of Holmes' and Balwani's expenses and there isn't anything left to give back.
https://tether.to/en/transparency/#reports
It might be still called React but will be completely different. How similar are React + hooks + redux to React of 4 years ago? We call both React but it's hardly similar.
Fast forward 10 years from now...
This is an old debate surely? My first awareness of it was probably related to Django's settings.py back around 2007 but I got the feeling from discussions then that it was a discussion that had been bouncing around for a long time before that.

The counter-argument is that declarative configs inevevitably sprout programming-like features - and if they don't someone will write code to generate them.

(disclaimer - in true HN fashion I haven't properly RTFA'd - dinner is nearly ready and I'm feeling bold)
Can you not use a standard USB to ps/2 adapter?
As much as the not running solar panels.

And when it does produce (99% of the time), it absolutely crushes any amount of solar panels.
> Is that anti-competitive forcing all sellers to sell your product at the price you want it sold?

Yes. And it's not supposed to be ""your"" product after you sell it to a retailer.
Yes. That is like the definition of anti-competitive. Apple is abusing its power as a manufacturer to gain an anti-competitive edge in the retail side of its business.
France is not like the US. Trying to do this will get you in trouble.
Verification, Impersonation, Twitter Blue
https://tomaszs2.medium.com/how-rust-1-64-became-10-20-faste...

https://news.ycombinator.com/item?id=33306945
Not true that "most" bootcampers are gone. Please don't spread misinformation.
It's a clear and obvious win for the US, US goals in the area, and general US goodwill, after we lost so much. And yet still, there is a significant portion of the Republican party that is strictly and vocally against it.
> the most decadent luxury currently possible.

Hey now, if he only has $38B that means he can't afford to buy Twitter until Elon finishes destroying it.
He just fired thousands of people who are good at things he isn’t, so I’m not sure I agree with your first sentence. But to your concluding question, yes that’s something I’m also intrigued by, and have yet to see any evidence of.
Yes, and I'm one of them. I'm not moaning at them about the price, but I think it's fair to consider what they are actually saying. They are telling users that v1 is now completely unsupported. That means, if you bought v1 last week, you cannot expect any compatibility support moving forward. The bugs that already exist? Those aren't getting taken care of either. People like to point out that they've owned Affinity products for a long time, and therefore have gotten their value out of them. I've owned all of the Affinity products for quite a while, so I've gotten plenty of value from them. I also have a (quite) expensive Adobe subscription. But at the end of the day, Affinity was marketed as the answer to subscription bloat. They aren't the first company to have to walk that back a bit with major version releases. They should have a deprecation plan in place for gradually winding down v1. Stopping all new features but still releasing compatibility and security fixes is incredibly common in software when major versions change. Instead, their answer is to cease all development an support immediately.
5 Tools I Used To Build a Component Library
The interest rate is, yes. The monthly payment, no.
And surely the buck stops with the Tether Foundation, who stand ready to cash Binance out, and they won't need to dump a bunch of risky assets and possibly not net enough to meet Binance's needs
> Besides they're no longer their products

This is correct for used devices, or course, but people in the wholesale chain will have signed contracts agreeing not to sell below MSRP.

It’s called “undercutting the channel”, and it’s very frowned on in the physical goods distribution industry.
Google is bringing its VPN to Mac and Windows PCs
Have you tried anything to solve this? Are there any products you've come across that try to solve this? I also have this problem but I'm not aware of any companies that are trying to solve it.
What's bizarre about asserts being disabled if you explicitly ask for it?
VLSI was also the major ARM-based designer / manufacturer at the time, there was almost nobody else building SoC on ARM.
> He's repeatedly betrayed user trust, and eventually what goes around comes around.

This. Yes.

Facebook came within a whisker of establishing themselves as the central communications hub for the planet. They ruined their own business from greed. Grew it huge (instead of long steady growth) and it has collapsed.

Greed

It would not have been a good thing if they became "... He's repeatedly betrayed user trust, and eventually what goes around comes around. " so we are all better off, probably.

I hope the story of Zuck and FB become business school lessons on "greed is bad and will destroy you". Not what they taught me at business school (I was there in 2008) but they should have
I think I'd do what your landlord is doing if I were in that position.

Having a long term reliable renter, which I'm sure you are, give them a rent that is a good deal (slightly below market), and they'll stay. Even if your rent doesn't cover mortgage and expenses, eventually you or other renters are going to buy the property for your landlord, and that's worth a lot.

Especially if home prices are up 50% - keeping your rent stable and you there paying it means your landlord is getting a spectacular deal.
It really does lack empathy. It's disappointing. IDK why you're getting downvoted even though you have a point here. React is open source and it's an organization by itself. It will survive. Worst case scenario: one of the OSS leaders will fork it and get help from others. Easier said than done, but that's one of the options that ppen source provides you.

For the lack of a better example, when Bill and Melinda (Gates) got divorced, people were worried about the Gates foundation. They even posted about it in their official note of separation to the community. Now, that makes sense. Asking about an open source project that's already quite stable, right after Meta lays off employees is in poor taste.
> Are parking lots so profitable, they can support this significant cost?

Costs are far more than offset by savings.

The savings in electric bills from schools with solar panels often topped millions in each district, and many have been able to adopt the technology without shouldering any costs up front.

“If you’re conservative, we didn’t ask you for more taxes, if you’re liberal, you love the green concept,” said Michael Hester, the school superintendent in Batesville, Ark., where solar arrays paid for teacher raises. “It’s a win-win.”

https://www.nytimes.com/2022/09/15/climate/solar-energy-scho... (archive: https://archive.ph/U5Alc)
Sometimes times are so bleak you need humor to really process it all.
I.... don't buy the initial example. Google maps is still an imperative list of directions. It just keeps track of the current pointer for you, and is able to reroute. If anything, that is an example that a dynamic action plan is more adaptable than a static one.

That said, declarative clearly has advantages when it can work. You probably still want a "break glass" way to see what the actual steps that will be taken are, but can get surprisingly far without that.
We were thinking about buying for ourselves but opted not to.

However we did hedge that decision by buying my mother in law an apartment and essentially becoming her landlords. We timed it as well as we possibly could have and locked in 2.5% on a 30 year in December of 2020.
ah yes. now that you say it, i recall they did that for Terminator 2.

https://www.youtube.com/watch?v=D0xp74uIZO4
It should be pretty clear by now that some members of the GOP are willingly doing things for Russia, whether by order or pure stupidity.
Yep the idea of declarative winning out over imperative is nothing new. Yet for some reason, most deployment systems make you go through an imperative flow if you want to orchestrate releases.
Not an audit
That's just using a wishy-washy slogan to take credit for other people's work. None of the technologies that associate themselves with web3 had anything to do with stable diffusion.

For SD, web3 has been worse than useless, because machine learning has been hindered by the miners hoarding GPUs.
This looks great!

One minor thing I'd like to see, and I don't know if this is to do with the underlying calendaring spec, is the differentiation of physical location and online meeting.

Some events may have both and I have found the "Join" buttons on desktop notifications for Outlook/Teams to be pretty convenient.
I think all in all AI is a danger for everyone in the industry and there's no reason to sugar coat it.

Pure economics makes whatever hopeful expectation of advantage created by the AI generated medium irrelevant for anyone with a livelihood in the field. Being the creative genius may allow you to retain your employment, but rest assured, your income growth will decline and the next generation coming after you will be making less. The value of graphics will decline and so the money earned by the people making it will also decline. You're making truly creative work? Great, a company can just take your rendering and use it as the basis for an AI generated image to remove any licensing requirement. Good luck trying to prove original ownership. And who needs creativity anyway? How often are graphics used in commercial/retail/media enterprises really breaking the mold? Whatever shortcomings mentioned are already being mitigated by add-on AI systems (Tencent's ARC for instance) so there should be an expectation of rapid improvement in the coming years.

People employed in the field will likely adapt away from non-lucrative image generating work eventually, but the transition will be pretty painful and the overall effect will likely constrain incomes for creative work in general.
> As a really simple example, one of the most frequent things I see from juniors using git GUIs is adding files to a commit that they didn't intend to (say stuff that's not in the .gitignore, but doesn't belong in the commit). In the CLI, they probably don't know about -a, so they would be forced to add files/directories individually and think about what to include. Most GUIs I've seen include a "Stage All" button front-and-center, which is very tempting for a new user to click (or, worse, they make staging an opt-out thing). I do not know if this specific example is the case in GitHub Desktop, it's something that I see regularly.

I agree with your general point, but on this specific point I'd be remiss if I didn't mention that I see an insane amount of people regularly use `git add .` to add every file, because they don't realize they actually want `git add -u` (only add already-tracked files) 99% of the time.

But as a counterpoint, since your example is about giving devs a limited set of commands, you naturally wouldn't be giving them `git add .`. But it's definitely something that frequently comes up in crappy git tutorials.
Currently discussed here

https://news.ycombinator.com/item?id=33530356
> Banks usually give a better rate for a longer term loan.

I think, only in rare circumstances, like rates being unusually high, such that they will almost certainly go down.

Locking in rates costs money. Nobody will give you a reduction in risk for nothing. Often they are a bad gamble, because if you're in a long term loan, even if the rate is variable, the length of the loan itself provides the averaging to de-risk that.

Most people work with spot rates for all sorts of stuff they consume. You don't get to negotiate a 30 year rate on steaks, milk or gasoline. You can still buy those things when prices are low and average things.
That makes sense... Since we generate specifications for an API automatically, it would be much more efficient (and accurate) than other fuzzing tools :) We'll definitely look into doing that, thank you for the advice!
Do you see a <homepage> anywhere where you can join my cult, you cuck? It's pretty damn obvious your life goal is to chew on some green paper, you sub-human expendable. I get that how I 'phrased my comment' might be seen as 'weird' by your types; you probably get that I used to code.