skysight-inc/HackerNews huggingface dataset:
Airlines such as Ryanair in Europe do this.

One of the regulations that airlines in europe are required to adhere to is that they're not allowed to advertise up-front prices that come with additional non-optional fees. So the ticket price advertised up front has to include all mandatory fees and taxes. Optional fees (hand luggage now being the latest, priority boarding, checked luggage) can be extra.

Payment processor fees cannot be extra. At least one needs to be free. So in reality, it's not necessarily the cheapest processor that's free, but it's the least popular one that's free. That way, for all the common ones, you can now charge a fee and tick the regulatory box, while still screwing your customers out of more money.

E.g. Visa Electron is free, Visa Debit/Credit, Mastercard debit/credit and Amex all come with fees to use.
I worked for a while in a restaurant in the US while I was a student on an exchange VISA and I found this system absolutely wild. As a zero-experience teenager new to a very temporary job I felt I was given way too much arbitrary power over people's payment cards.

(everyone signing for card payments did also seemed weird at the time as, while there was no contactless back then, we'd been 100% chip-and-pin in Europe for some time, but I think that was a more well-known oddity of the US)
My expectation about a counter offer is, they just need to keep you until they can find a replacement for you.

That said it all depends on your reasons for leaving. If it is environment only, then definitely no. If it is more money maybe, but expect to be high on the layoff list should the economy turn.
Not necessarily new optimization passes, but currently the order of optimizations is more or less fixed (you can technically rearrange them between builds but almost nobody does this AFAIK except that one Uber dev optimizing iOS app size). Even worse, there is no globally optimal order as what is good for one codebase might not be optimal for another. E-graphs can find the optimum arrangement for all codebases without requiring excessive amounts of memory and so could produce better output from compilers.

They won't find new equivalences on their own though. I doubt that is even possible, you can't in general prove equivalence of functions without also solving the halting problem. Also, even just defining the equivalences we know about are often only valid in certain circumstances that I doubt a computer could figure out in the general case.
I don't think editorializing is a simple on/off switch, and I think substack is trying to do "editorialize less" rather than "don't editorialize at all".
A duopoly is not much better than a monopoly.

What makes you think it will go from maximum profit to approximately zero profit?
@rhamzeh yes, it's all in the FAQs. If you're not satisfied, I'll shoot you an email and we can resolve it.
Amazon faces new lawsuit alleging it fixed book prices
I just delete my docker logs when the disk is full and get a 5GB space :)
The boat
is stuck
>"conviction is still upheld"

There was no nullification in that particular case. If there was judge can say whatever s/he wants but there would be no conviction.
Because it is a full headless web browser (older version of Webkit).
Here's a list for clearer viewing, cover art etc.:

https://letterboxd.com/luxpir/list/kurosawas-top-100/
Weekly stock reports newsletter – Investomail
Investomail is a free weekly newsletter highlighting the most promising stock forecasts. You get an email with a stock report every Sunday. Stocks are selected based on analysts' ratings. The newsletter serves as a filter of stocks, providing you with only the stocks analysts think are a good buy. The newsletter is not financial advice and you should always do your due diligence.
There is a function/type duality that goes very deep into foundations of mathematics, but it's a conceptually different one than the one proposed in OOP. So I don't think interpreting all those similarities as being OOP is quite correct.
Nah. Far too coherent, and far too many lowercase letters. Not enough blaming of everything on a left-wing conspiracy.
The author gets it. I hope every developer dealing with microservices will read this.
Beautiful. I'm glad to have read this.
Not around text field searches.
Something as simple as searching for exact fragment with punctuation (think function header) often does not work at all.
> Additional fees for the privilege, not so much.

But you understand that as the end customer, you end up paying the fees anyway, even if they are not visible in the bill? If your customers were unhappy about the extra cost, maybe you were not open enough about them or maybe the customer did not think your service worth the extra fee? After all, if the end customer is the one paying the fee, hotel has no incentive to try to get the customer past the OTA. They get the same money anyway.
The former isn't how most OOP languages do it and those two options aren't the only two options.

Personally, as someone who mainly uses Clojure, I would rather type:

(blocked-by? user other-user)

With that said, it really doesn't matter which of these options I have to type, because as usual, the syntax is less important than the semantics and all of these options can work with or without OOP. Now, OOP isn't bad per se, its just a tool. It depends on how you use it.

I do buy into the Clojure notion though that there is a problem with most OOP languages and that is that they conflate multiple concerns and features into objects. Give me the features to mix and match as I please, instead. That is, if I want to keep my data and my functions together, great, but if I don't, also great. If I want to do polymorphism with objects, great, if I want to do it without, also great. Let me choose, based on the problem I'm solving.

I tend to favour a functional-first approach, but will use OOP as it makes sense or when it makes the API easier. To me, immutable state (where possible) is more important than an avoidance of OOP. I also write a lot of C++ and I won't shy away from creating some classes where it makes sense.
The objective is to lighten the ship. Moving the light containers isn’t optimal.
Since the sides of the channel are much more shallow than the middle, it's not floating in the water as both ends of the ship are stuck on the bottom.
Show HN: Free Easter Illustrations – Commercial use without attribution
I haven’t been to Europe for a few years so my memory is vague, but at least in Canada, you can enter a tip on the point-of-sale machine (and waiters/bartenders will get very aggressive if you don’t leave enough, despite the stereotype that “tipping is only a thing in the US culture”). Other than that parenthetical, does it work the same way in Europe?

For those who don’t know, in the US it works like this: a paper receipt is brought, which you write a tip amount on in pen and then sign. The total is then manually entered into the computer later on. Absolutely medieval technology.
Living every single day being treated as a literal piece of disposable garbage by everyone around you, all while not having a quiet place to sleep or a little piece of the world to call your own can damage one's mental health to the point where they can no longer function as productive members of society.

You've experienced homelessness, so you shouldn't need me to tell you the consequences of living that way long term.
>I’ve just moved teams to be the only Senior Engineer [...] I want to restructure things to enable the team to start working in a red-green-refactor loop.

What's the team currently doing, and why?

>So our culture is to only refactor incrementally as we go along....which makes about as much sense to me as only washing dishes when you are cooking.

It's more like avoiding the trap of thinking "we have a pile of dirty dishes from the past several days, why even bother wash the dishes we used today".

Something useful to reduce technical debt is at least not incurring more of it starting from today. You still have the debt from the past that you'll pay gradually, but not adding to it is a start.

Engineering is about tradeoffs which is why extreme people tend to have last programmed in 1981, or are great at architecture diagrams and cute acronyms. I'm busting nibbles.

>I want to restructure things to enable the team to start working in a red-green-refactor loop.

In my opinion, you add the tests then you restructure things because you'd have the tests safety net that tell you and your team that you broke something.

So...

I'll assume you're using GitHub or GitLab.

Right now, you can add a test that succeeds all the time, then configure the CI on GitLab (adding a minimal `gitlab-ci.yml` just to have a pipeline, trigger a CI job that's triggered when you push your changes, and display the coverage and status badges on the `README.md`.

Once you have a pipeline that practically does nothing but that works, you can get to work with the following approaches:

- New code should include tests (independent effort to get things under control)

- Look at the code coverage, and start writing tests for the untested code. As you are new to the team, this will speed up your understanding of the codebase. You also are being useful for the team actually putting your money where your mouth is.

- Add issue templates to the repository for features, bugs, and incidents. This reduces the varience in issue quality and the team members aren't faced with a blank page staring at them. The issues will have a nice structure with comments on how to fill them so they be the most useful. After a while, the members will be able to parse these issues really fast. The issues will have tags (bugs, features) and you'll be able to quickly filter and focus on bugs. It'll also surface similarities. If a bunch of bugs are about a certain part of the system, a module, or a functionality, you add a test harness first, and then you can refactor it or improve it so it sucks less.

- You do that systematically, you'll see consistent progress without the whole thing being a big deal or stressful because it doesn't require "major changes at once" either on the code or on the workflow.

This is what we did for our team. Add scaffolding. Gradually, but consistently improve the workflow. It's a good habit and the process must not get in the way, or you'll have non-consumption and people won't do it.

Here's more: https://news.ycombinator.com/item?id=26552842
"You know what I don't do? Try to harass, intimidate or rob them. Do you know why? Because I am not an animal."

I think you should gey off your high horse, comparing people to animals is not cool.

For starters, you misunderstand the basics - are you actually sure you could harras a person with billions of dollars, connections and lawyers?

Because, doing that in Russia is a good strategy to end in beried in the forest.

In Brutain in 1800 judges were not paid by the state, the people being judged paid them. And the more they paid, the 'better' they were judged. That was official policy. Now obviously we call that corruption.
A better way would be to explode one medium sized nuke under the ship, wait a few seconds then explode another and then start exploding nukes behind it until it's going fast enough.

Project Orion did contemplate a 400m diameter ship weighing 8 million tons....

https://en.wikipedia.org/wiki/Project_Orion_(nuclear_propuls...
Though quite an interesting solution and an appropriate one for ML, I think, given the sporadic and temporally limited nature of the availability data they receive from the stores. After all, that a store has 100 cans of soda right now doesn't mean they'll have any when my order is being picked in 2 days time.
I’m sorrry but your “Edit” makes you look pretentious. There’s a simple alternative: people just found your comment boring or irrelevant...
These corporate funds work for new, shiny OSS products - they generally stay clear from the bedrock, the core technologies that keep the world running, like, for instance, NTP.

For that, there's Loadsharers, a true community-run distribution network, which I invite everyone to go and have a look: https://esr.gitlab.io/loadsharers/
And Discover, though those two are far less common than Visa/MC/AmEx.
Thanks, that makes sense of course and I'm pretty sure me[-20 years] knew this but it has since been flushed out of the poor brain tissue.
A small nitpick, Erlang doesn't implement the Actor model. The similarity of Erlang's processes and the actors, defined by Carl Hewitt, is accidental as stated by Joe Armstrong multiple times.

Edit: Actors doesn't run concurrently.
Those 8 pis have all their hardware, though. The Ryzen needs all the rest of the hardware to finish off the computer.
They do. You can use something like puppeteer to use a headless Chrome or Firefox to generate PDFs from HTML for you.

https://github.com/puppeteer/puppeteer/blob/v5.3.1/docs/api....
WeWork agrees to go public through a SPAC deal with BowX Acquisition
Developers are well paid in the US because of VC and monopoly backed business models. To go coop is to abandon those options, one explicitly and one implicitly.
It's a shame Firefox just ditched the SSB project instead of fixing the bugs and making it visible for PWA use. They say it's because people weren't using it, but it was another thing that was hidden behind about:config and had some glaring bugs which two strong reasons why people probably weren't using or even know about it.
There are also pushy managers who would insist on slapping another function onto an existing microservice and then cut time spent on writing tests, just so that he can meet his targets and get a bonus. Then the app with time will start to perform worse and worse but when it happens, the manager will be long into a new gig and the developers will get the whipping. Then they'll get new developers to fix the mess and once it gets stable, a new manager will start to insist on adding that function to an existing microservice... and the cycle repeats...
You can just undervolt the Ryzen and it will still run cycles around the Raspberry Pi while consuming less power if you are into that sort of thing.
This is often the excuse we hear for why modern software is bad: "well, normal people don't care about that", a strawman argument that implies anyone who does care is abnormal and therefore worthless.
A bit off topic, but anyone who ever played SnowRunner or MudRunner can probably relate. Quite often when you try to rescue a truck, you flip it over, and now require another truck with a crane to come over and load the cargo again.
The canal generated 5.61 billion USD in 2020 [0] so it is costing them 15 million dollars a day in lost revenue. Shipping companies now have to go around Africa which costs uses more fuel and has other costs but now they don't have to pay the toll and I'm betting the spread between the toll price and the additional cost of going around Africa isn't very large or Egypt is leaving free money on the table.

[0]: https://en.wikipedia.org/wiki/Suez_Canal_Authority#:~:text=I...
Sure, but one of the most common causes of disks being filled on Linux is either the kernel or some process running as root filling the disk with endless repeating log entries.
Tech and IT Managers Can Help Make Great Startups
Startups come in many different sizes and flavors. When talking about Tech and IT managers, we can include the Chief Technical Officer, Project Manager, Software Engineering Manager, or Team Leader.

Sometimes, it can even be the Tech Guru – the gal or guy in a non-tech company who happens to be savvier than everyone else when it comes to tech. If you are in or aspiring to be in any of these roles, you can have a profound impact on the success of your startup – and even more mature companies. Not all of these tips will apply in every instance, but here are twelve tips you can apply to drive your startup to greatness.

1⃣ Company priorities and financial situation
2⃣ Define standards early and enforce them
3⃣ Hiring and onboarding
4⃣ Get to know your team and make them feel appreciated
5⃣ Honesty and transparency
6⃣ Be available for your team
7⃣ Delegate
8⃣ Promote career and skill development
9⃣Experiment and automate
Technical support for other departments
*⃣ An extra tip – get some sleep!

Learn more inside
Or, as it was known back then, the baa-ckchain.
The style of writing indicates to me at least that OP was not writing to be technically precise to this level. Since it is abundantly clear to you that the payment was a bribe then isn’t the natural conclusion that it was a bribe and that “fee” was used to convey the idea that there was a cost involved that couldn’t be avoided?
> 2. This assumes that multiple helicopters can't work in tandem (which they can, from what I understand).

Do you mean two helicopters carrying a single slung load? That is not practised anywhere.

Tandem loads in military terms refer to a single helicopter carrying two slung loads, one in front of the other.

As far as I know, none of the helicopters mentioned above are rated for sling operations with 40ft containers.
History of VR
>For most US cities you could cover the payment needs of most riders with something from Square installed in the car.

That's a good example of driver-centric thinking instead of holistic thinking that considers the paying passengers. Consider: what if the customers/passengers actually prefer the convenience of not having to mess with an extra payment transaction step before exiting the car?!? With service like Uber, passengers can just get out of the car immediately when they arrive at their destination. No whipping out the credit-card to swipe. No exchanging of QR codes.

Always think of game theory and consumer behavior preferences.

Adding "Square payments" as a driver-platform "solution to avoid complexity for the programmers" is adding another reason for customers to avoid using it because you added complexity to the customers -- and therefore you have less revenue. There are always tradeoffs.

Whenever anyone thinks "Problem <X> is trivial, and the solution is just to do <Y>," ... you have to think a few chess moves ahead as to what the actual paying customers will do that may negate your "solution".
“Everything I Have Learned I Have Learned from Someone Else”, David Nolen (2013)
So you expect that whole food delivery business will collapse?

I don't see that coming because it is 2020 and we have: smartphones in every pocket, easy payments from those smartphones, it is super convenient to order via such platform, in the end lock downs basically mandate food delivery.
I was unaware of the Hephy Workflow/Deis Labs background, but yes, porter.sh has come up recently and we are aware of this.

For some clarification, Porter was initially started as a remote dev solution (similar to Github Codespaces) as part of the S20 YC batch, which operated in a very different space. When we pivoted to the current PaaS solution, we kept the same company name/domain, but didn't think to check on the name collision after we pivoted.

We're going to address this at some level, whether it be a name change or much more explicit clarification in our Github repo, since we're also unhappy about the name collision. Sorry for any confusion this may have caused.
> It has cost us $30 billion dollars, so far...

This valuation is based on Lloyd's list's valuation of Suez traffic at ~$10 billion / day, but surely that would require all traffic to be permanently lost (rather than delayed) to add up to a concrete loss. Spoilage might be an issue with some cargo, plus there's other costs to delay, but I can't imagine the eventual loss will be anything close to $10 billion / day (excepting obvious large unknowns like market speculation).
This heavily reminds me of Papers, Please [1] by Lucas Pope. Great game and a good example of how to tell a story through mechanics rather than a linear storyline.

[1] https://papersplea.se
Please don't promote the idea that this is limited to the Islamic world.

Low-level corruption is just endemic across much of the world, whether it is notionally Muslim, Hindu, Christian, Buddhist or none of the above.
I'm a web dev so I only use it for web apps but you can certainly use it beyond web applications.
A police officer in rural Colombia can be negotiated with to obtain an outcome that is satisfactory to all parties. Try that at the San Fransisco DMV, even if they want to help you they can't because the process is the process.

There are pros and cons to both systems. The low bribery systems tend to curb the worst behavior (no amount of donating to the right causes will help you put a toxic waste processing plant in Manhatten) at the expense of really screwing the people who are edge cases.

The equatorial developing nations tend to have a lot of class divide and racism problems that get nastier in a regulatory environment where everything is fuzzy. If you want to see a bribery based regulatory environment done right look at eastern Europe from 1980-2000ish (years vary depending on where you look).

HN loves the "hurr durr stupid poor countries and their bribery" trope but for those countries routine bribery is mostly just a cultural workaround for the fact that they can't afford a massive administrative state to grant you a stupid variance from their stupid zoning rules on your stupid garden shed (or whatever). They're effectively pushing decision making onto the leaves of the organizational tree and cutting the organizational tree out of the payment loop somewhat. Yes, it goes awry sometimes but it's not like western bureaucracies have any lack of similarly bad outcomes.
Not that common. A bigger plague (though somewhat later if my memory seves me right) was toolbars that was sneaked into every other application.

The power consumption alone of JavaScript easily shadows that. Pretty much no desktop computer in the world can go in lower sleep states because of javascript "idling" in the background. And a decent percentage of CPU cores are constantly pegged at 100%. Imagine the number of batteries that has prematurely died because of the stress of javascript - when all the user wanted was to read static text.

Enabling ActiveX for your bank site is hardly the same. The real issue was running it on another OS than windows. Happily trade it for what we have today though.
I believe this article could be more effective and less politically oriented if there were more specifics about how US primacy is different from British primacy 100+ years ago, for example. History shows that “empires” come and go—and their hegemony is always under some sort of attack-so there is nothing new about that dynamic. Something will change, and there will be a new empire. And we will all throw stones at them, I’m sure.
Fart Proudly: A Letter to the Royal Academy – Benjamin Franklin (1781) [pdf]
You could say that for any marketing activity. You don't expect a hotel to add an additional fee for the fact that you seen an advert in a glossy magazine, or for providing their own website for that matter.

I'm sure you are aware that the entire travel industry, predating the advent of OTA, works on a commission basis.
Who said I'm convinced that i uniquely thought of that?

What's wrong with you? This isn't your first demeaning comment.

This is literally a place where people tend to discuss/propose things on and get feedback. HN can give a unique insight of commenters that ARE experts on the topic, even while the poster is not. Not many people here see issues with that.
I don't think you needed the post, as a whole.
Why? There'd still be more than enough traffic to keep both full, there's no need to compete on price.
It wasn't the fastest, but I think that now browser (and CPU) tech has moved on since then, it'd probably be a lot smoother. I remember using it once to coordinate specs on a small contract job and it worked pretty well for that.
That is not true. The energy efficiency will go down if you downclock because the static to dynamic power ratio will increase.
> within a few weeks

Haha, no. Just no.
Has anyone but RMS diagnosed RMS as having an autism spectrum disorder?