krab

It doesn't matter whether the service is paid or not.

I would say GPL constrains some freedoms of the code users to provide some freedoms to the end users.

It's not entirely clear what counts as derivative work with regards to GPL. There is a lot of corner cases and workarounds in the real world. It becomes even less clear when you widen the definition of distribution.

It will only grow - as new scripts will need to be interpreted, new features will be added.

I understand it as "not only alarmist sources but also a reputable journal".

You're right. It just doesn't seem to create much issues in the application code I have experience with.

Due to the pain that concurrency is in Python, the codebases I've seen mostly shared data only via external processes (queues, databases).

I was very surprised to read the article. I think in the code I have in mind the borrow checker would only add overhead.

The most frequent errors I see in the Python webapp code are: 1. logic errors, especially around concurrent DB transactions, 2. type errors (missing values, improperly modeled data), 3. performance problems.

You can always add this feature but it's problematic to remove it.

It might be different for purely online deals. But for companies working with a local agency, it's definitely not worth the reputation risk.

They don't give a fuck because they know no case when clicking "accept all" on a random website got someone in trouble.

The other professions have the same choice as programmers - either sell their service and worry about all other stuff, or outsource these worries and get hired.

There is no shortage of jobs where programmers are getting paid for programming.

That's why such agreement wouldn't be legally binding in a big part of the world. The users in turn know it's more or less safe to click "accept all" on a random website.

The error flow is often but designed by the product people because they might not have full view of what can go wrong.

I actually prefer to buy and sell used cars with wire transfer. Within EU, they're usually instantaneous within a country and overnight internationally. I don't have to worry about carrying larger amount of money - when I was purchasing my first motorcycle, it was literally almost everything I had at the time. If something goes wrong and I got scammed, the money can be tracked a little bit better than with cash.

EDIT: And in this case, there seems to be an exception specifically for cars.

The author presents a perfectly reasonable alternative with argumentation supporting the position. There is nothing in the article about being forced.

Personally, I find the described model - especially with trusted "notaries" - much better. It might also help with open source financing.

At multiple companies I worked for, they concluded the backwards schema changes are not worth the risks and testing overhead. It's usually quick enough to issue a hotfix.

With rollback, you always risk losing data - remember, you're doing it when something didn't go as you expected. What are the odds, the rollback will break something further?

These were all Postgres shops, so schema changes within a transaction - that can be rolled back safely if it fails in the middle.

There are other attributes as well - the combination of colour, size, shape and surface features might be unique in many people's mixes.

I guess the "bug in the laptop" part would be the hardest at the time of auto-updates.

Assuming someone builds a database of vulnerable displays and related exploits, your software can choose the correct exploit because HDMI sends the display model. But if the display is not connected to the network, it would have to exploit an unpatched vulnerability over HDMI in a laptop that connects to it. Not entirely impossible but the time window might be slim if it's not a zero-day.

To be fair, crypto has some value for illicit transactions and money laundering.

It's not obvious to me whether this value is greater than the mining costs or not. I think the value is in fact smaller and therefore the valuation is just a bubble.

Yes, exactly! The people who want to make money selling drugs have much harder time. It's possible but inconvenient (and in this case also dangerous).

Imagine cryptocurrencies are banned in your country.

The exchange of goods and services you describe might work between individuals. However businesses are much more visible. OK, you run a business accepting cryptocurrency payments for your goods. How will you explain it to the tax office? What if someone tips the police you accept it and they try to purchase something? OK, so only the small businesses will do it. They're numerous enough the police can't catch everyone. How will they transact with the bigger companies that can't accept illegal payments? Purchase utilities, tools etc. OK, somehow you make enough money with legal payments to pay your bills and keep the cryptocurrencies only as profit. Now try buying a car or a house with illegal currency.

Everything has a workaround, but if the state outright bans cryptocurrencies, the market will be severely crippled.

If I know someone else is on call and he's competent, I can sleep better.

I don't know much about the technology - the lack of larger installations is a red flag. Anyway, I tried to calculate with the numbers from the document above with the following assumptions:

10 charging stations, 6 cars per hour per station, 100 kWh per car. That makes 6 MW peak consumption for the whole "gas" station. A capacitor storing 6 MWh (60 cars served, no incoming electricity) would need to have 120 m³ of storage. Google says that a gas station storage size is between 30 000 and 40 000 gallons (110 000 - 150 000 l) so that seems comparable. Another way to look at it - 200 m³ of storage is a building of 10 x 10 x 2 m, without the need to manipulate flammable liquids.

Not sure about the investment costs (the doc says 5 000 cycles but no cost estimate), how long the peaks are and other aspects of running a gas station. Still, it seems the order of magnitude is about right.

Or swappable batteries if we standardize on a few sizes. You can then charge those slowly.

However that brings problems with quality control - a worn battery costs less than the new one. Maybe a model where the customer doesn't own the battery?

Gas station could store the energy (supercapacitors?) to average out the utility load.

According to https://www.energy.gov/sites/prod/files/piprod/documents/Ses... the technology seems to exist.

The parent post argues that if you invest in learning or tweaking open source tools, they're useful to you over a longer period of time than the commercial counterparts in general. I don't read it as absolute. Just an explanation of their preference.

I absolutely love the smell of coffee.

However, I don't enjoy drinking it in particular. I like it with a lot of milk and I find the taste of some coffee varieties quite interesting, enjoyable even. But not enough for daily drinking.

Our colo even offers managed Kubernetes on top of the rented hardware.

Yes! Make a new version of the language that includes the used extensions, freeze it for a while, add a few chapters to Learn You a Haskell. That would improve the experience of a learner who wants to move from toys to real projects.

The level of risk and needed effort also scales with the user base. So supporting local Gitlab or similar for 20 users is more like a 0.05 FTE, whereas it can easily be 0.5 FTE or more for 100 users.

A bit more than half of the added value in Germany is created by companies with less than 500 employees and less than €50M yearly turnover (Mittelstand). There is in fact a lot of specialized machinery vendors providing significant value.

Not sure what are their IT needs, but I guess the larger SMEs are the target market for this service.