skysight-inc/HackerNews huggingface dataset:
Vendors have 2 core requirements to continue operating: get new customers and keep the existing ones. Getting new customers requires constant innovation, marketing spend, providing value, etc. Keeping existing customers only requires making the pain of leaving greater than the pain of staying.
The UAE's secret hacking team of US mercenaries
This is a long detailed answer, that fails to answer the question.

The Answerer seems to have answered the question 'will python suffer the same fate as php'
Way harder to remember a hash using base64. Hex is much more manageable and you still only need to remember 4-5 digits usually.
The only time you need more than one of the possible meanings at a time is when you want to make a pun. When translating, you'd have to explain both meanings, ruining the fun, but it's not a real barrier to expressing the content.
And yet you are still there...
is there an equivalent setting for chromium?
So is a friend or neighbour who stops by once a day to feed the plants, water the cats, and empty the mailbox.
You probably don't need electron to do that, it could be done by any end user. Wondering why it isn't being done!
> Why it needs so much resources just to send a few bytes of text?..

Waste. It doesn't cost them much[0], and they don't seem to care on an ethical level about it either, and wastefulness allows them to achieve their business goals faster. Until there's a business pressure for it, things won't improve, and I have no idea what such pressure could be.

--

[0] - How many of their users are captive anyway? I didn't choose to use Slack, some non-tech folks at the company I'm working with chose it. Elsewhere, someone in the community of a technology I use also chose Slack. So now I'm forced to use them in both cases.
One year of taking ice cold showers in the morning
I agree that it's not remotely as drastic as telling the French they have to speak English, but it seems fairly comparable to telling programmers they have to wear dress shirts.
I can't help but interpret 'Slack' as an abbreviation of 'Slackware', always, in whatever context. This leads to some curious confusions.
Maybe it doesn't speed up cedar tree growth but it certainly affects algae and fern growth.

http://theazollafoundation.org/azollas-uses/as-a-co2-sequest...
>Ad companies are filth.

To be honest, I am wondering more and more if those aggressive unwanted advertisement are having an impact on peoples behavior and emotional baseline. Similar to road rage. Except you dont always sit in your car, but most of us spend significant parts of their lives in front of screens.
Python Design Patterns (2016)
Could some one explain what 'digital' means in this context?
Well, causality is hard to establish here. Note, post north sea oil the UK had an economic boom that saw it move ahead of both Italy and France on many measures. The UK did not use Marshall aid for industrial investment, but it did build a welfare state, and did eventually pay off its debts of 200% gdp.
This is a pretty bad article.

In the last example (which is actually the most common case in practice), they give wrong instructions. They should only revert the bad commit, not all the following commits. Reverting everything is impractical and useless, and if you want to do that you may as well use revert (which is still a bad idea).
Looks awesome. Random feature suggestion: Visual hunk staging like in magit for emacs. Super useful.

Edit: You can see that feature here: https://magit.vc/screenshots/ under "Staging Changes"
Show HN: Calculate monthly salary in Slovenia in 3 steps
Some ideas for improvements on the title:

"Her husband went to a doctor. What happened next will leave you speechless!"

"10 times doctors were wrong. Number 7 brought tears to my eyes!"

"The 100 funniest videos of doctors' accidents."

edit: English is not my native language, it's "speechless", I think.
See https://pijul.org/ (and its inspiration, http://darcs.net/ ). It's actually something quite different from both.
If you download a release of FreeBSD, that image will not contain a desktop environment. If you look through there source code, no desktop environment, something also true of Linux. Of course you can install third party packages, including a range of desktop environments.

So, considering FreeBSD has no desktop environment, and likely little desire for one, how are they being ripped off by Apple's failure to give them their DE?
No problem! It's an easy mistake to make.
Sabineblogging
Something to consider: large states (e.g. Texas) have more small, remote towns that small states (e.g. Utah) do. If you're worried about making sure roads, water, education, power, and postal services make it to the outback, the large states have more people voting in that direction than the small states do. Those interests are still represented. And there are businesses on the coasts (e.g. shipping firms) which are keenly interested in the care and feeding of the families of workers managing grain mills and rail lines in South Dakota.
Surely you can fix that without having physically separate copies of the underlying chromium engine?

edit: I realize now this is a joke thread... whoosh.
It’s not just portability that’s an issue with lambda. It’s also churn.

Running on Lambda, one day you’ll get an email saying that we’re deprecating node version x.x so be sure to upgrade your app by June 27th when we pull the plug. Now you have to pull the team back together and make a bunch of changes to an old, working, app just to meet some 3rd party’s arbitrary timeframe.

If you’re running node x.x on your own backend, you can choose to simply keep doing so for as long as you want, regardless of what version the cool kids are using these days.

That’s the issue I find myself up against more often when relying on Other People’s Infrastructure.
I do agree to some extent, but when you look at the sovereign wealth fund that Norway has that still generates huge amounts of revenue and then look at what the UK has left... it does seem like the word "squander" is appropriate.
you should check next.js and now deloyment, even faster/easier setup for JS stuff
> Being capable of intelligence and being intelligent are not necessarily the same thing.

My argument was against what I saw as a notion that human beings must always express the intelligence we all undoubtably possess, simply because we do. I don't think that's the case. It's not about using straight logic, either: it's about empathy, and the emotions that influence (or even underline) our decisions, and the bigger picture, and whether being angry right now is worth our time...

I think we all can be like that. I think we're not encouraged enough to act that way.

There are certainly selfish motives to every single one of us – and yet, some of us are superb at overriding those motives for the sake of a better act, some struggle to the point of giving up, and others yet barely even tap into the altruistic motives.

I think it all has to do, in half, with the environment we're in. Generally speaking, fear promotes fear, and empathy promotes empathy. There's about 40 to 60% to do with genetics (the number I've seen was 55%), but that much we can't control.

We can control our environments, to an extent.
Ask HN: What is your motivation for learning a new language?
Besides obvious reasons like "my new job requires it", what drives you to learn a new programming language instead of just using the ones you already know?
Not the most important matter but from the FAQs

> Where does the name come from?

> Pijul is the mexican name of Crotophaga sulcirostris, a bird known to do collaborative nest building.

About technical stuff: the mathematical theory of patches, commutability, etc are nice properties but any versioning system has to fight a very uphill battle nowadays. Incumbents (mostly git) are very entrenched. I'd like to hear which reasonable expectations the authors of pijul have.

By the way, do you ever mistype it? How about a two or three letters official short name?
Instead we are encouraging users to download arbitrary binaries bundled with a browser that can be controlled and updated remotely. It’s not clear to me this is any safer.
And by "…Go the fastest." I assume you mean compiled languages.
I've really looked for a simple CLI tool like that, to replace my current usage of Gitg. Thank you!
Geoblink | Software Engineer| Madrid, Spain | mostly onsite|

We’re a fast growing startup that has already raised close to $8 million in investment. You would join the POI-Acquisition team as a Software Engineer, working with the Data Scientists to acquire and process hundreds of POIs on a daily basis (and more as we keep growing!). This will involve tasks to develop the back end (Node.js and Python) of different applications (back end services and internal web apps) to read data from databases or CSV files and process it in different steps, creating automated pipelines when possible.

Salary: 32K-45K Euros plus stock options, and personal development budget. We also offer other great benefits.

Email: jobs@geoblink.com or apply here: https://www.geoblink.com/work-with-us/
Could the Russians Decide Canada's Next Prime Minister?
Hi, thanks for your interest. At this time we ask that everyone work at the Berlin office since we're a pretty small team and it's important for the social dynamic.
Currently not on the roadmap – for what it's worth, the majority of apps perform their Electron updates at different times, so you'd still have the same number of binaries and files as you do today.
TurboPFor: an analysis
PostgreSQL Connection Pooling with PgBouncer
> Maybe this article should start with "defined as people born between 1980 and 2000 in western countries"

I've lived in both east and west and I can tell you that millennials have similar issues everywhere when it comes to the scope of this article.
I can also tell how wrong are both sides about each other's cultures which is indeed a different discussion.
Then you get into the issue of keeping apps and runtime in sync so you don't get issues with older apps not working well with a new version of the runtime required by newer apps...

You end-up having to keep multiple runtimes and hoping they don't step on each-other's toes...

After a while you're still downloading 200+MB runtimes to run your particular app that still requires Runtime 5.05 and hasn't been updated to work with Runtime 6.12 that is required for newer updates of an app that used to work with Runtime 5.84...

Maybe a better idea would be to make Electron's install specific to each app and only include the bits you actually need so it's a 30MB bundle instead?

Just wondering if calling for a runtime isn't going to make things worse in the long run.
It 's already often a pain to install an app that target any framework version in particular that may not be installed or may conflict on some user's target machines. Sometimes it's unavoidable, but I'm wondering if this is really the case here.
There is:

https://www.sblack.online
Good points, but it remains to be seen whether the portability of large serverless apps is sufficient to prevent the providers from squeezing their customers once they are deeply established.

The fact that there’s three major cloud providers (who will at the very least compete on customer acquisition) is a point in favor of this, but it’s definitely an experiment. In my mind, this is as much about negotiating power as it is about technical tradeoffs.
Github let's you host images in issues. So what you can do is make an issue with all your images in it, and immediately close it.
The problem with articles like this is that that present it as being a de facto justification for "I don't believe the dr".

It's a variation of survivor bias - you don't see articles "s/he thought the dr was wrong! But the Dr was right!" because they obviously don't produce headlines.
Hi, Felix from Slack's Electron team here.

Slack co-maintains Electron together with GitHub, employing multiple core maintainers full-time, contracting those who can't join us full-time. We've also just hosted (and paid for) the first Electron conference. We're also maintaining a fairly large number of electron-userland modules.

tl;dr: That page might be misleading, we're investing heavily in Electron.
Eaze | SF | Full-Time | https://eaze.com
Eaze's mission is to improve lives by providing safe, secure access to the highest quality cannabis products. We are seeking passionate, talented and innovative leaders to join our world-class team and help shape history.

Here are our open roles:

- Senior Backend Engineer: https://jobs.lever.co/eaze/b3f8d324-afb9-4e06-9ac8-24e1c1bb7...

- Senior Frontend Engineer: https://jobs.lever.co/eaze/82e5d883-70fa-412f-b743-f7f63e4e7...

- Senior Infrastructure Engineer: https://jobs.lever.co/eaze/b98a0286-6dfa-45f6-9212-826b532c3...

Tech stack: Frontend: React / Redux. Backend: Node/.NET/C#. Infra: AWS, Terraform.

More at https://eaze.com/careers
> I find it necessary to invest substantial effort in calibrating a new question. Before I ask a candidate a new question, I try use it to mock interview at least 10 people I have worked closely with.

You could do that some process, with the interviewee.

It would be a great way to see how collaborative they are.

i.e. you say "I've never actually worked through this problem myself, so I don't know how deep the rabbit hole is, but let's give it a crack and see what we come up with together."

Sounds a lot more like real-life to me than a manufactured question you've already worked through to the nth degree.
How much to post a job (2018)
What Makes a Growth Engineer Tick?
And the reason his employer uses it is to ensure everyone can interrupt everyone and give each other more work.
Yes. Models are basically programs, and GIGO absolutely applies: Garbage In = Garbage Out. :)
Discord is not more polished for decent sized companies who need to worry about regulatory compliance and things.
Using Electron is a travesty. Why not something like "sciter" ?
There's no chance we go for 64bit transaction ids on the tuples themselves - the space increase would be far too big. The overhead of tuple headers is already a problem, and xmin/xmax are a significant portion of that.

There were patches however that kept an 'epoch' (the upper 32bit of a 64bit transaction id) on a page level. Plus some rewrite logic when transactions that are too far away from each other to be represented as an index from a base epoch are about to be present on one page. That'd allow to effectively have 64bit xids.

The in-development zheap storage engine basically does something roughly akin to that, removing the need to perform freezing when a table becomes older than ~2^31 - safety-window transactions.

The transaction id that the system internally has effectively already keeps track of of xids in a 64bit manner, albeit in a somewhat over-complicated manner by keeping track of an epoch separately (there's a patch likely to land in the next version to just go for 64bit there). That's why you can see e.g. txid_current() return 64bit transaction ids.
If you bothered to read the link I posted, you would see that PWAs are native apps in UWP with full access to the same APIs as .NET and C++ have, if distributed via the store.

Same applies to PWAs on ChromeOS (naturally given its nature), and Google is ramping up the same capabilities on Android with their initial release of TWA.

Yep, there are a few OSes currently left out, it is up to their masters to follow Microsoft and Google's footsteps.
Pijul keeps touting "patches" instead of commits, and they show how to record and unrecord these patches. But how do you actually work with such a repository? How do you handle merge conflicts? The documentation does not even describe how to resolve conflicts, just that you can procrastinate and save the conflicts "for later"[1].
There is probably technical merit in Pijul, but the documentation and marketing sucks.

[1]: https://pijul.org/manual/conflicts.html
Same, I don't understand why more people aren't like this
Edit: my bad, it wasn't clear in your post that you were promoting your tweets using Twitter.
Your site is really performant Bogdanp. Mind me asking if you use a paid host or something like netlify?
I used to work at a valley big corp (social network) and interviewed a ton of candidates. My approach was as follows:

- Review candidate's resume and side projects to get to know more about them. This helped with getting to know their work and finding things to discuss beyond the interview exercise.

- Before diving into the exercise I would out right tell the candidate what I was looking for in regards to the exercise; e.g. "I'm not looking for a complete/perfect answer but I'm looking to have a conversation about the pros/cons and edge-cases. You can write on the whiteboard as little or as much as you want to but either way let's have a discussion. Let me know if you feel stuck at any point, and I'll make sure to let you know if you are/aren't on the right track. If you don't know/remember something just ask me; it' fine, nobody knows everything."

- I didn't put too much weight on whether the candidate gave a complete answer or not, or how much I had to help them. I basically asked myself a simple question: "Do I feel like this person would be a productive contributor here and are they someone I would be able to work with?"

- I always did my best to go into the room with a relaxed and conversational attitude. I was there to pass the candidate and not to fail them for random reasons.

- I passed most people and only failed some when it was somewhat obvious to me that they really lacked some very basic foundational pieces, or when I felt like they weren't someone I would want to work with (for various reasons).

Towards the end of my career there I started to really dislike interviewing because I would personally put so much effort to passing candidates, but they wouldn't get hired because other interviewers left feedback like "I helped the candidate too much" or "they didn't even know what a TRIE tree was" or "they struggled with X" or "the solution had bugs" or "the solution wasn't complete".

They interesting thing was that the same interviewers that failed candidates for seemingly random reasons, were also the ones who left confusing feedback or not enough feedback. Also the same interviewers either treated candidates poorly or they showed boredom and agitation.
Hmm. The way they measured this value is interesting. They tried to figure out how much money they would have to pay people for them to agree to stop using Facebook for a period of time. The numbers were a bit startling to me at first: in the hundreds or even thousands of dollars.

Suppose I said to you that there was a thing I used regularly, that I knew was bad for my health, but I felt compelled to keep using it. And the thought of abstaining from it was so difficult that I would give up hundreds or thousands of dollars to keep using it.

What does that sound like?

You could describe a drug addiction with exactly the same words.

I'm not saying Facebook provides no value whatsoever. But I think the measurement in dollars is not purely a measure of value; it's part value and part compulsion.
Good point, but no. If you have architected your apps properly, decommissioning or sunsetting services or individual components should already have been designed and planned.

I know, I know... It's almost never the case.
That's just laziness on your part though.

Using an old version of Node is just going to leave you with worse performance and potentially security holes.
We can't use transaction ids for that however, because they're necessarily assigned by the time a transaction starts to write, whereas visibility is determined by the time transactions commit. Snapshots, the datastructure that determines which transaction's writes ought to be visible and which not, use transaction ids as cutoff values however, to make visibility determinations cheaper.

A second large reasons why we'd not want to go for randomness is that we need to store data for each transaction id, namely whether it committed or not. If we'd assign them randomly we'd need to keep around a lot more of that data, and accesses would be a lot more expensive because there'd basically not be any locality.
Agreed. Perl failed primarily because it took 10+ years to come out with Perl 6. By the time that Perl had first class support for the object oriented paradigm, new paradigms had started to gain traction, notably functional. PHP almost suffered the same fate, but wisely decided to backport some of the improvements.

Python is unlikely to undergo a 10 year rewrite, although some of its recent decisions such as the 3.0 split and the more recent decision to make async a reserved keyword have shown some of the more problematic tendencies.
tptacek: the reddit article there is a bit flawed (as uhoreg tries to gently point out in the response). the reality is that we provide decent E2EE stacks on web, iOS and Android which get used in the flagship client (Riot) that most people use. These are pretty solid and getting better, as per the SAS verif and cross-signing work. Other clients like Seaglass which build on the same SDKs obviously get the same experience. I would argue that these provide a decent decentralised alternative to Signal, WA or Wire, especially if you run your own server (given we don’t do log minimisation on matrix.org).

Now, there’s a long tail of other random clients which don’t do E2EE, which is inevitable given doing a good secure job of an independent E2EE implementation is obviously tough. But is that actually a problem, given the most usable mainstream clients do have it?

It’s a bit like declaring that the Web is in a disastrous sad state because of the number of HTTP clients out there which don’t have a CSS engine in them...
What if we interpret Moore's law to say that transaction speed will double every 2 years?
gitin is a minimalist tool that lets you explore a git repository from command line. You can search from commits, inspect indvidual files and changes in the commits, see ahead/behind commits etc. It is an alternative and interactive way to explore the commit history. Also, you can explore your current state by investigating diffs, stage your changes and commit them.

When I was building https://github.com/isacikgoz/gitbatch I had to decide whether use git2go(libgit2) or go-git with my project, I choose go-git for gitbatch and I wanted to try git2go with another project. gitin is born with this idea but it is now a handy tool for me to use everyday. I am happy with git2go(libgit2) and consider using it on gitbatch too.
Yup. :'(
This is why I have come to the (anecdotal) conclusion that one can only integrate into a group / society / culture when one learns / masters the language.

There are many nuances that imply the importance of particular details in the hidden meaning of the wording. These get easily lost when one does not fully comprehend the language used.
Which is the best online meat store in Chennai?
Chinese investment in infrastructure is often a diplomatic trap
There are also a terrible cost of running just on one database, the dependency on just one provider.

In business you should never depend on just one provider. This provider could be the best in the world, now, because it has amazing management. But people die, or are hit by a bus, or get crazy after a divorce or just retire and they get replaced by the antitheses.

In my personal experience, real portability has great benefits on their own. Design is easier to understand and you constantly find bugs thanks to running your software in different architectures, compilers and so on.

At the end of the day, it is the quality of your team. If your team is bad, your software will be bad and vice versa.