skysight-inc/HackerNews huggingface dataset:
I hear ya, after my work day I find it very hard to do much more than chill. I am most productive in the morning, and try and find 1 hour before starting my day.
I also recommend the book Atomic Habits by James Clear - as he has helped me try and build a habit I enjoy around my side projects.
Not the fediverse, but I'm working on moving Gurlic's backend to matrix and opening up the code. Which means people should be able to host their own matrix server and run a Gurlic instance. Still a heavy WIP though.

I don't see why it wouldn't work. Matrix is a solid protocol to work with. The only thing I want to be careful about is ensuring that the UI has none of the weirdness usually found in decentralized apps.
First Ever Programmable Organism
Do people on SS get particularly narrow upper bodies? It's not very obvious from SS presenters, videos, etc. With alternated bench press and overhead press, are there groups of muscles that it misses completely?
Label Studio Latest – Data Manager for ML/AI Applications
> Elastic pulls in $500MM in revenue

Not taking sides, but for comparison, Amazon makes that much revenue every 12 hours.
Absolutely! Blog about this is a wonderful idea. Sounds really interesting.
Can I subscribe now?
Russ Roberts on whether it's more effective to help strangers or people you know
> insane profits AWS is making

Do you have numbers on how much AWS profits from Amazon Elastic Search service?

Have you checked the profits from Elastic for their offerings?

Have you compared them?

How do you quantify "insane"?

Honest questions. Just a data person.
It's possible for there to be no good guys in a fight. They are both multi-billion dollar corporations looking out for their shareholders' interests. "Open source" is being thrown around by both sides as a marketing/goodwill tool, nothing more.
This is how it works in Texas at HEB and Central Market. It's about $10 to do curbside grocery pickup, more around $15-$30 I believe for delivery, which is done through Favor, a delivery subsidiary of HEB.
Forgive me for expressing my frustrating for a moment here:

What is with this new generation of developers (I don't mean new as in young since I meet people in their 40s espousing these ideas), who make all these high-minded arguments about how evil it is to profit off of someone else's work, when literally that's what proprietary software is for. If you don't want someone to make money with your code, don't give it away freely, sell it.

Instead, what Elastic did was they made a beautiful piece of open source software, licensed under Apache 2.0. Because it was Apache 2.0, organizations were comfortable building Elasticsearch into their stacks because they knew that they couldn't get Microsofted. Additionally because it was Apache 2.0, hundreds of contributors who are not affiliated with Elastic submitted patches to their codebase.

Elastic used its position as an open source maintainer to grow Elasticsearch to be one of the most important pieces of software in the world (nowhere as important as linux or arguably lucene but still in the top echelon), and then once it did that it decided to lie to the community, pull the rug out from under them and switch to proprietary.

Now to be clear, I actually think this won't even make them more money, it will just hurt their brand image and incentivize high-quality Apache 2.0 feature-rich forks, so really it's just an absurd blunder. But I am so unbelievably frustrated that people keep espousing this reverse entitlement attitude that you espoused here: the idea that an open source vendor gives away their software for free, intentionally, so that they can benefit from the community and vice versa, and then suddenly now somehow I'm an asshole if I've been operating a service that uses Elasticsearch. It's completely backwards logic.

To put it another way, as an open source maintainer, you don't owe anybody your time. You are free to tell the people opening github issues and bug tracker tickets to go fuck themselves. But similar, nobody owes you anything, so if you yell at someone using your free software for commercial purposes, now you're being the entitled asshole. They don't owe you any money.

You people seem to think open source just means "source available". It's SO MUCH MORE than that.

[/unhinged rant]
AWS has a point there (although I personally don't like their wording, open source is only a side effect here, it's more about how Amazon can charge for it also in future).

It only makes me sad that AWS makes a lot of $$$ with their elastic SaaS because of their size and for that reason can monetize it better than the original authors. Feels very Amazon like for me.

At end I have the feeling it could be all avoided if Amazon paid a little bit royalty to Elastic and both sides would have talked more and better together.
That's because twitter actually has content moderation policies in place that they do their best to apply. They're obviously not perfect, but again, the whole reason the app store banned parler was that they had no workable moderation plan in place. Twitter does.
Well, in general! Had other automakers copied similarly futuristic and overly-stylish cars, we would've ended up with a completely different design philosophy perhaps?
A solution expert usually brings a baggage of knowledge of previously working solutions in the problem space, knowledge that has been acquired over many months of hard work

Short gigs where you being in a solution, point a team/company on the right direction and then jump off compensate for the accrued knowledge transfer more than for the hour worked

Think of it like a top end athlete, they aren't paid for the few hours of play, but for the years of training that keep them competitive
New Year Profit Bot Review – Done-for-You Free Traffic and Sales
What Exactly Is New Year Profit Bot?

New Year Profit Bot is a brand new software which allows you to get 100% FREE traffic and SALES easily.

All of the online marketers and affiliate marketers want to get 100% free and genuine traffic so that they can get the most conversion and get a lot of sales.

So let’s break it down how exactly how New Year Profit Bot works.
you can check out here?

https://warriorplus.com/o2/a/kqm1k/0
>> itsoktocry 2 hours ago [–]

>> When I was part of a union it amounted to 2 hours of wages per month, not exactly onerous.
reply

>> elefanten 2 hours ago [–]

>> Counterexample: the nascent Google employees union is taking 1% of total comp.

Not sure it's really a counterexample as there are - in theory - about 200 work hours per month, so 1% of comp is pretty much equivalent to 2 hours of wages per month.
I absolutely agree and that's where the price differential is coming in, but it causes some perverse effects to the wage market. Is the work of the person solving that 5k/day problem that's then sold to ten clients worth ten times as much as the work of the person who's work is only sold to one client?

I think it's important to recognize the semi-arbitrary source of where this value is coming from and understand that while employees impacting a lot of customers are indeed creating a lot of value the work they are doing isn't significantly different from the work made by folks with more modest salaries.

Basically, at the core, I think there's a significant ethical question here and I would highlight the relative infancy of the industry. It's likely that in a few hundred years all this incredible value creation will be highly commoditized and that innovative development will be relegated to academic pursuits that companies only adopt and bring to market after a lot of investigation and research.

Uh hrm - as another parallel you might compare this to speed running. Right now we can do relatively simple things to dramatically create value (time saved off the run) but as time goes on and the run gets more "perfected" then the ability to shave time off the run (or create value for the business) will require a lot more investment of effort. I'm not certain if this will happen since everything in how development works points to this being a really hard state of the industry to accomplish - but looking at economic trends it feels inevitable that eventually it will be more profitable to, for instance, produce a cheaper better whatsapp then being the first market entrent into the coveted Deciduous Tree Vlog Platform market.
A quick google image search doesn't bring up any rusted DeLoreans either.
Sure you can call someone a dick for abiding by the terms of the agreement that you set out, but that doesn't mean you're right.

"Hey here is some software. You are free to use it without paying me."

"Ok, we'll use it and not pay you"

"What, how dare you?! You dick!"
Don't try to compete on same market, provide differentiated offering. Focus on consultancy, custom development (plugins etc), on-prem deployments. You are the foremost experts of the software, capitalize that instead of trying to compete on ops stuff which is AWS bread and butter.

That might follow with recognition that your market might be smaller than what Elastic co has so far projected, and even it might not be enough to sustain $15B market cap, but bursting that bubble should not be all doom and gloom. Being small does not equate not being successful.
Mainly HN, also I have a pretty curated Twitter following (tech and startups) so Twitter is second in line, then Indie Hackers, and lastly Tildes at https://tildes.net.

Tildes is a new one for me, but I am enjoying its simple UI and smaller community.
Perhaps. But also, given the regulation, you remove opportunity for those that are looking for the type of employment you discredit from accepting it from employers that want to offer it. I very much appreciate the ability to step into the gig economy when I need to. I assume you mean well, but I wish you and other's who agree with you would kindly butt out and let me make my own decisions.
Many museums started in the times of yore, and became first tier through donations by powerful and rich patrons (and/or by the state).
From my personal exchanges with people on Twitter on various contributions to projects in the Kubernetes ecosystem, I have frequently seen that some AWS employees (and sometimes the companies they partner with) want to make it seem like AWS is _really_ doing open source with real contributions. Every time I pointed my finger and asked, I got a response from such people "you should know not all contributions to the open source are code".

I'm not gatekeeping what "real contributions" are: You can fund development of OSS, you can provide Project Manager support, you can publicize and organize events (for the sake of the tech; not sales), do DevRel for something, provide UX/UXR/design support etc. They're all real contributions.

But for some reason, AWS contributions to 3rd party OSS projects stops right at "it works fine on AWS". It's kind of a meme at this point.

Disclaimer: I work at GCP on Kubernetes/OSS.
Mark Felton did cover that as well on YouTube.
Having gone through an unexpected, young death where nothing was recorded, I’ve come to the opposite conclusion: anything significant enough to care about already has next-of-kin processes established such that the Right Person will be able to sort it out.

Indeed, when it comes to stuff like finances, at least where I live, touching them post-death creates issues when the legal channels confirming there’s no contest over next-of-kin haven’t been run to ground. In those situations, having a password means nothing.

This doesn’t mean you shouldn’t prep a will and have processes in place, but it gave me a lot of reassurance that I did not need to worry so much about this.
> The lesson I’m taking away from this is just use a license like they’re using now from day 1.

Sure, if your whole business model is “sell a SaaS”, then making the whole offering an open source product that is simple for other people to host and offer an equivalent (or, if integrated with other offerings you don’t have, often more compelling) service is a bad choice.

But people choose open source licensing for a reason, and against competing software, a proprietary license can be a negative feature which makes it harder to grow mindshare and prove out utility.
> in that the statements of fact and of logical implications are valid.

See for example https://slatestarcodex.com/2019/05/07/5-httlpr-a-pointed-rev... for a slightly different take.
Right. Almost an impossible task based on precedent. But my point was that it isn't like the system as designed can't handle way more transactions than it currently does.

If you have a sports car that is limited to do 15mph, but can actually do 215mph if you remove the artificial limiter, then you don't need a technological breakthrough to get the car to go to 215mph.
Well I'm clearly not an advocate of fully free markets when there are natural monopolies or societal interests higher than profit.

And I'm not bitching, I'm discussing.
Software developer.... Turned agency owner... But now I have sold my agency after 8 years I and am a "Technical lead"... But by the end of this year will be back to a Software developer (which I am looking forward to!)
I thought street crime was a pretty terrible business for most?
https://www.youtube.com/watch?v=5UGC2nLnaes

Also, bank robbery isn't usually very lucrative, and they've made it harder and less lucrative over time. "According to the FBI a bank robbery averaged a take of $4,000 in 2009, which may not have been sufficient to yield the thieves a positive return on their enterprise. You see, at today's prices, the robbers would need to expend $4,442 for the guns, bullets, and masks used in a typical bank robbery." http://bastiat.mises.org/2014/09/the-basic-economics-of-bank...

Some crime has been made pretty unprofitable.
https://www.youtube.com/watch?v=CqNEQS80-h4 - Luke Dashjr "Briefly, Why Block Sizes Shouldn't Be Too Big"

https://www.youtube.com/watch?v=92AYj_9W7x0 - Why is Block Size 1MB Andreas Antonopoulos

There's simple trade-off between decentralized and bandwidth requirements. If you raise the limit you reduce the pool of those that run full nodes thereby centralizing the network at which point you're undermining the point of a decentralized ledger.
It is a little bit more complicated than that.

If the webapp can solve $5000/day problem but there is literally millions of people that can do this, you are certainly not getting a share of that. Somebody else is maybe going to be rewarded for spotting an opportunity but the most you get is a "market rate".

The only way you can get paid proportionally is if you are literally the only one that can solve the problem and you know it and they know you know it.
Steve Jobs said something like Dropbox was a feature, not a product. I think Bezos feels the same about literally everything. AFAIK Azure/Google have actual partnerships with the Elastic stack, partnerships that assumedly benefit both sides and have staying power.

Part of me wonders if AWS always had planned to do this, and they were just waiting until it made business sense to fork (ie they had features and a new direction in mind but neglected to implement them because Elasticsearch was good enough as is). The alternative part is just 2 big corporations not finding a way to get along. Which means without clear direction and careful stewardship I'd expect the forks to just be cleanroom reimplementations or something like that.
Pointers are virtual addresses but memory is accessed physically. All of the means of translating virtual to physical are in the CPU. If you are proposing throwing out virtual addressing, I imagine you won't get a lot of support for that idea.
To Elastic: if you're a $15B [0] company you don't get to be a victim by appealing to your customer base to whine about how your competitor is profiting "unjustly" from a decision you made that led to your growth in the first place. Choosing Apache2 license ensures your OSS gets traction, but then you'll have to live with its consequences when Amazon comes knocking on the door.

[0] https://google.com/search?q=estc
I'd phrase it backwards: these people think it should have the appearance of open source and get all the benefits (contributions from community, widespread adoption), but legally and ethically speaking it's closed source and they get to make all the money.

They seriously have this entitled attitude that because you used the free software project that they started, that now they're entitled to that money. It's patently absurd. Imagine if Linus Torvalds went around with that attitude, claiming he deserves to be a trillionaire because of the absurd amount of value Linux has produced. (And ironically Linux is a more restrictive license than Elasticsearch)
While it's great that AWS has indeed contributed fixes to upstream Elasticsearch, they link to 9 PRs that are generally on the trivial end of the scale. (Though I don't doubt the PR that adds a missing synchronized keyword might have been gnarly and time consuming to debug, and that diff size does not necessarily correlate to importance)

For a project AWS was making hundreds of millions in revenue on four years ago (as per an ex AWS employee), patting your own shoulder for such a trivial amount of contributions is a bit disingenuous. They might have contributed more, but if there was something significant, they probably would have mentioned.

Notable new features like "ultrawarm" they did not attempt to contribute upstream, nor open source at all: https://aws.amazon.com/about-aws/whats-new/2020/05/aws-annou...
- Developer in San Francisco (a rare bird I was),now a developer not in San Francisco.

- A beautiful expensive poop dodging masterpiece, equip with an ambience of liberal virtue signaling socialists.

- A beautiful cheap poop disposing masterpiece, surrounded by honest hard working colonists.

- Bigger. Cheaper. Not often you get more, for less.

- 10 months

- To realize my dream of owning something other than debt.

- Big. Cheap. Guns. Land.

- Learning to walk with my chest held high, embracing plaid, and the increased size of my chin.

- It picked me, with calloused hands and honest gaze.

- Do it. Save your chin.
is there any actual hope for the GPU? is it based on any architecture for which there already exist Linux drivers?
If you came from a BSD, then you (were supposed to) already know why make install is not a good idea. Although Debian package management was not particularly similar to FreeBSD ports and packages, the fundamental idea was the same.
To Win More Sales, Stop Selling
My two cents:

Open source is a type of generosity. Generosity is good in the software world because the rules of the game benefits everybody the most when everybody are generous. I believe it's similar to prisoners dilemma but with even bigger benefits when we are all generous.

However, it's also a tit-for-tat game. When others start to be greedy it makes some sense to be greedy yourself. Thus short circuiting the game and making the playground worse for everyone. Until we realize that generous is better again.

So tying back to your comment. Yes, open source contributors doesn't expect something back but they can only hope that others at least pay it forward.
That does seem clean, but I would worry about normal people being confused by it. Having (business's name)@myname.com already gets a lot of questions / confirmations / confused responses.
Could not disagree more. The premise of this piece is that dieting is just willpower, beating addiction is the same, an entirely individual problem.

The reality is that the incentives are what society is asking for, with ethics etc acting as constraints only, rather than actively rewarded. In that formulation it is inevitable (and optimal) that some people will skate to the edge, and if the edge is poorly enforced they will increasingly go over.

Policies must address the overall actual effects, not just a chimerical ideal.

(It is even more ridiculous coming from someone in psychology.)
> Also, ideally, you'd publicly host the Dockerfile

Docker doesn't make it easy to produce a reproducible config. People commonly write Dockerfiles with stuff like this in them:

RUN apt-get install -y my-favourite-package

And then which version of my-favourite-package you get depends on what is the latest one on the update servers at a time. Maybe a new version is released tomorrow with a regression bug that breaks everything.

There are ways to get around this problem, but the default ways of doing things in Docker doesn't encourage reproducibility.
I remember I wanted to read Principia in my first year as a Physics student.
Never got my hands on it but got my hands on other old physics books and I think it a bad idea to study on those.

The new ideas are usually not presented in the clearest way. They often are shown from the point of view of the author, who is a genius and has his own way of seeing things.

Better to study from people that have digested them, discussed them with peers and have a point of view on things that has become the standard in the scientific community
> This strikes me as odd. In my experience, traditional OLTP row stores are I/O bound due to contention (locking and latching). Does anyone have an explanation for this?

Yes. My CTO, Avi Kivity did a great talk about this at Core C++ 2019: https://www.scylladb.com/2020/03/26/avi-kivity-at-core-c-201...

Let me boil it down to a few points; some beyond Avi's talk:

• Traditional RDBMS with strong consistency and ACID guarantees are always going to exhibit delays. That's what you want them for. Slow, but solid.

• Even many NoSQL databases written (supposedly) for High Availability still use highly synchronous mechanisms internally.

• You need to think about a multi-processor, multi-core server as its own network internally. You need to consider rewriting everything with the fundamental consideration of async processing, even within the same node. Scylla uses C++ futures/promises, shared-nothing shard-per-core architecture, as well as new async methods like io_uring.

• Between nodes, you also have to consider highly async mechanisms. For example, the tunable eventual consistency model you'd find in Cassandra or Scylla. While we also support Paxos for LWT, if you need strong linearizability, read-before-write conditional updates, that comes at a cost. Many classes of transactions will treat that as overkill.

• And yes, backups are also a huge issue for those sorts of data volumes. Scylla, for example, has implemented different priority classes for certain types of activities. It handles all the scheduling between OLTP transactions as highest priority, while allowing the system to plug away at, say, backups or repairs.

More on where we're going with all this is written in a blog about our new Project Circe:

https://www.scylladb.com/2021/01/12/making-scylla-a-monstrou...

But the main point is that you have to really think about how to re-architect your software to take advantage of huge multi-processor machines. If you invest in all this hardware, but your software is limiting your utility of it, you're not getting the full bang you spent your buck on.
Because, they are are the good guys? At least if you believe in open source, not the fake stuff that Elastic is peddling.
Laptops given to British schoolkids came preloaded with Gamarue malware
What if I told you that, more often than not, you could do your current work and get much more money? People, especially tech people, are quite awful at extracting their full value.
Elastic is at least open about reasons. AWS pretend to be an OSS champion. Compared to other players Google, MS they do the least amount of OSS work. Hypocrisy is really worse than selfishness. It definitely shifted my neutral view of AWS.

I can still spin ElasticSearch cluster for my backend and I have somehow open license. Where is open source version of Aurora, Dynamo, DocumentDB, Neptune or Redshift? Where is anything OSS from AWS that is useful outside interfacing with AWS services?
I'm eagerly waiting for mazda to announce the electric miata with knobs, levers, and no autonomous bullshit.
You know, modern cars, which all feature straight edged unpainted stainless steel.