omegabravo

0 bytes?

as someone who lives there, they're not. Nor is that what is being suggested, it's critiquing car-centric cities where not having a car is needlessly difficult. Population 250 isn't going to ban cars, but the city may discourage driving and provide ample facilities for those who don't have a car.

I was confused why someone would possibly configure the voice to be quiet and raspy.

Seems like there's an issue with Firefox that was causing it. Chrome voice sounds "normal" - like TikTok.

topic isn't about India's telecom market to be fair. I'm happy to see a wide range of opinions on the topic.

> One might say this is an advantage

I'm baffled that anyone could propose this as a good thing. I've worked in industries that are supported - just smaller than the US and the price gouging is substantial. Parts will be designed for the US market, we need to adapt. Bonus points when buying incompatible European / US designs.

Solar panels, batteries, and wind turbine have all the necessary ancillary parts in warehouses close to where they are needed. They also have all the expertise, the cranes, the transport regulations nailed down.

I don't know what two companies pay, so I clicked two based on reputation and work. If I knew one paid more, I would have absolutely chosen that.

Go is not cool, it's boring and readable. I don't need a diagram to understand what the code is doing compared to Java. I say that with deep respect for the JVM and all the problems that are solved with it. It's an incredible ecosystem.

I'm productive in Go because I realise most of my time isn't spent typing, it's thinking. I shy away from over abstraction and lean heavily towards composition.

If you're solving a problem that requires complicated type system - don't use Go. If you're writing a UI - don't use Go. If you like 20 layers of abstraction - don't use Go.

If you're writing a product like I am, with similar constraints, then Go is an excellent fit.

People for some reason like to pretend everyone is working on the same problem that they are, and have the same requirements they do.

This person doesn't like Go, and that's fine. I have no doubt I'd be able to solve their problem in Go, and I have no doubt they'd be able to solve my problem in Java.

building it is the most valuable part

how is this measured? Because if it's by total vessels it's a poor comparison. If it's by total aircraft carrier, it's also a poor comparison.

Basically measuring this is difficult, but this is contrary to my only knowledge of this which was a Wendover video (that was an enjoyable watch), but I wouldn't hold in the highest standard.

as I understand it, it would be http://captive.apple.com

so that the captive portal can intercept and write their own login.

How would they have got a proper CA signed cert for a domain they don't own?

HSTS will only make a HTTPS connection. Without the valid certificate, they should get a warning.

The only way this "works" is if a captive portal pops up a browser to a site that looks the same like amaz0n.com. Password manager wouldn't popup, but many people don't use them.

Faking DNS also won't help with the TLS warning, they won't have the certificate.

Basically, this shouldn't be possible with HSTS.

open dev tools, right click cursors.js - block this URL. refresh

Their employer likely has absolute control over their Windows install. My personal Windows laptop isn't allowed on the corporate network either.

If you're pushing bits and bytes you might want tight control over the runtime and guaranteed execution time. If you're not, I think it's perfectly acceptable.

strikes me as an outside observer, lacking in empathy for the characters.

Interesting perspective none the less.

I disagree, I consider that an absolute win of efficient engineering. Develop the feature enough that it lasts 30 years without needing to be fixed.

This interface was perfectly acceptable in the 90s, and it's perfectly acceptable today. Dropping a big graphic with a large circle button labelled format would have been worse. I say this as someone who writes my fair share of aesthetic user interfaces.

My takeaway is different. If your "temporary code" is sufficient to solve the problem, then it may last 30 years. If it was an actual problem, it would have been fixed by now.

You would need a pressure vessel and corrosion resistance, and potentially a pump driving up the cost.

solar panel with sand is mechanically and electrically much simpler

it suits my workflow since all windows are full screen on all the monitors. I either use alt+tab or super key to get the exploded view.

it won't suit all workflows of course

I find justwatch to be reliable. Sometimes I even find something new to watch on there too.

it's cheaper than IntelliJ, and is more resource efficient believe it or not

doing it on your phone only has one person querying it. Scale that to several thousand and it might appear different.

This is correct from my understanding, and glossing over the article and links is precisely what they're talking about.

Pipeline of taking data from one system, transforming it and loading it into another. There is a whole industry full of software products that facilitate this such as MuleSoft. It is referred to as ETL

I was surprised to see your succinct correct answer greyed out.

I expect that if you're wearing polarising lenses such as sunglasses, you can't see your phone if it's held in portrait or landscape.

I happen to agree, just trying to point out the miscommunication

The button is 44x44. The SVG is 30x18

Just pointing out that codes make it easier to provide translations and ability to switch between error types with more confidence than string matching.

Error codes should be accompanied by helpful messages so you don't have to look up the table.

Tailwind before tailwind.

It's strange, I never saw the point of it, however I saw the value in tailwind almost straight away.

I think that might be the difference in examples. The tachyon examples always look uninspiring.

Being able to read your code you wrote 2 years ago does wonders for survivability, which is a gross simplification of course.

It's a great language for some problems, horrible for others. The problem is people tend to talk as though everyone works in their domain.

I'm confused how _only less regulation_ can solve the problem. Famously, companies love less regulation so they can do what they want without consequence.

Good regulation, is quite effective. Just hard.