orra

Your proprietary software won't be a derivative work of most of G++, but it will likely be a derivative work of libgcc (compiler runtime), libc (on Linux), and libstdc++.

Anyway, running copyrighted software without a valid license is clear cut unlawful, at least in the EU. That's because running the application requires copying it (into RAM).

No, really, the law is that pedantic. "Loading" is a restricted act under Article 4 of the Computer Programs Directive.

Source code is, for the GPL, the “preferred form for modification”. Given the outrageous cost of training from scratch, plus the ability to fine tune models... I don't think it's completely ridiculous.

Edit: plus, the industry acts like models aren't derivative works of the training data. If true the source license is less important than the model!

I was going to say: because Falcon 180GB is open source, so you can run it for any purpose, without worrying about license restrictions.

However, it transpires Falcon 180B uses a proprietary license “based upon” the Apache license. Despite Falcon's claims to the contrary, it is not open source.

And that's disappointing because Falcon 40B is actually open source (and Apache licensed).

> Can't imagine poor people living in older buildings will ever get that

Less of a problem than you think. Car ownership is much higher in middle and upper classes, than working class. It's also less common in the densest populated areas, because residential off street parking is barely a thing in the UK.

I imagine there'll be a mixture of solutions: possibly-robotic services to shunt parked cars around (for the few charging spots), car clubs, battery swaps, fast/high wattage charging, converting substantially more street parking to low wattage charges...

Absolutely. Electrification is way (2x? 3x?) more efficient than producing and transporting clean hydrogen, or using an electric battery.

Using batteries isn't a goal. It's something we do when there is no alternative.

I was slightly mistaken in that it's 42% [1], not 50%+. But that's still a derisory figure. The cruelty of the UK towards children is absolutely real.

The two child limit, and associated rape clause, is punitive. If we look at UK families with three or more children, two million of those kids are in poverty [1]. Scrapping the limit would cost a token amount, and lift 270 000 [2] children out of poverty.

[1] https://www.gov.uk/government/statistics/households-below-av... table 4_5db

[2] https://edm.parliament.uk/early-day-motion/61220/the-twochil...

It's such a transparent lie. Most families in the UK with three children are in poverty. The UK punishes the child for existing, by denying it social security.

I'll admit, that's a fantastic third party effort. But there definitely isn't the same level of first party support as there is for zip files.

But other databases cannot access sqlite databases, because the file format is internal...

It's definitely short, but are you doing it for the side effects? Then I find .map() misleading. I'd much prefer a .forEach(), or a for...of.

But async/await is special syntax. I agree it's a nice improvement over using Task APIs directly.

That's clearly not a real policy. You can't trick a court with such obvious deception.

In particular, moderators have bosses, and nobody can believe moderators can do what the hell they want without their manager having a say.

> while enabling the social network to maintain maximum flexibility.

In other words, giving the employees absolute discretion isn't normally what you would consider giving the company (owners/directors) flexibility.

You can check in laptops; OP clearly misunderstands. https://www.tsa.gov/travel/security-screening/whatcanibring/...

There are stricter rules however for spare batteries, including power banks. https://www.tsa.gov/travel/security-screening/whatcanibring/...

That's why Excelsior is filled with safe, natural helium.

https://archer.fandom.com/wiki/Skytanic

Absolutely this. A series of commits dealing with different aspects (e.g. whitespace fix, minor related bug fix, necessary refactor, then the feature) is ideal.

For a start, it's easy to review, and easier to disect if something breaks.

When messy git history is provided (i.e. a history of the developer fixing their own code that they missed), squashing can be a reasonable fallback. But it's never the best option, IMHO.

> Why delude yourself?

Because bacon-cheeseburgers are tasty. Being able to eat something similar, without the ethical and environmental concerns, is a very attractive idea.

That's not what I said, and it's also not what we're talking about. We're specifically talking about Apple, who ship to customers all across the EU.

If a company offers better pricing to one market, it must make these offers accessible to everybody, regardless of nationality or country of residence. Apple don't let you buy apple.ie (Ireland) and ship to France.

https://europa.eu/youreurope/citizens/consumers/unfair-treat...

Any exceptions have to be objectively justified, such as postage pricing. Definitely doesn't justify huge differences.

Companies have long flouted these rules, so they were recently tightened up.

For physical goods, VAT is charged according to the seller's country. So in this case that is not relevant.

That's basically illegal under EU law, to discriminate like that. It's a single market...

I am glad that worked for you. The reason I flag it is: it may silently appear to work, but be heating up the cables without you realising it.

This is sensible advice. They are very convenient.

However I will clarify that although you can get great speeds with a flat Ethernet cable (thanks to modern manufacturing?), you must not use these to carry power.

I want to make this clear because first cables tend to describe themselves as Cat6 or whatever. This may be close enough in terms of signal/speed, but these don't use a thick enough wire guage to do PoE (Power over Ethernet), let alone PoE+.

(I am reasonably sure real Cat6 cables must support at least PoE, but it is hard to be certain when standards are behind paywalls.)

I was thinking of PSD (the original one), but it turns out that only required end of next business day settlement.

> Why are these API banks always in the UK?

I can think of 835 million reasons: https://www.reuters.com/article/eu-rbs-britain/corrected-uk-...

Plus, Open Banking and Faster Payments (which were EU initiatives before Brexit) maybe helped.

I believe it's an open question, the curvature of the universe, and hence whether the universe is infinite.

Others have already clarified that the big bang tells us the observable universe used to be tiny. In other words, the universe was much denser. It does not tell us the absolute size of the entire universe.

> today’s observable universe is roughly 13.8B years. By the time you travel to the edge of that universe

Careful. That's the age of the observable universe, not the size. The radius of the observable universe is 47B light years, which is larger because of inflation.

> Therefore you never get to that edge, making it infinite.

FWIW, I disagree with the conclusion. Finite but expanding fast is not infinite (disclaimer: mathematician not a physicist).

Why not? Simply, hubris.

That feels like an excuse. Windows compatibility mode is mature. The relevant APIs could easily return different values to buggy software.

Fair. But, at least later on, that wasn't universal. There's x.odd for development releases, and x.even for proper releases. GNOME and Linux used to do this.

Also it feels like a lot of projects used to use 0.x numbers, even when they were widely used and stable!

I'm afraid that's wishful thinking. JS compatibility is core to the TypeScript ethos, regardless of TypeScript's own popularity.

Besides, enums (?) aside, and ignoring typechecking, compiling TS is really easy right now. Switching to WASM is a high ask.