deafcalculus

Software might be a differentiator for a while, but it'll likely get commoditised. Self-driving doesn't involve complex UI with high switching costs and has little network effects / virality. And Google doesn't really have distribution locked down for self-driving cars like Search or Gmail.

The hardware on the other hand might not get commoditised so easily. It might have patent protection. If nothing else, high capital costs will mean monopoly or duopoly with enough profits.

HTML is fine. The problem is when JS is necessary to even navigate. Printing doesn't work well on those. They also tend to not work well on flaky internet connections (4G hotspot) because they load slides lazily or something. So, if it's not too much trouble, please provide PDF as an option for slides.

Here's a small thing that annoys me: Presentations in HTML. It feels almost like a form of DRM! Please release slides in PDF.

Flipkart made a huge mistake by trying to go mobile-only a while ago and is now mostly a smartphone shop. Hardly anyone I know buys anything other than smartphones (often Flipkart-exclusive) from them. Amazon now has a bigger catalog and better prices too.

Walmart could come along and directly compete in the market by themselves. Wonder why this acquisition is needed at all. There's hardly anything defensible in Flipkart's assets, and this acquisition isn't at a deep discount.

Huge percent of the audience blocks GA.

Why won't the simple approach of not allowing packages to break API compatibility work? Fixed some bugs or added new functions to a library foo? Keep calling it foo. Made an incompatible change? Call it foo2.

At least, this encourages backward compatibility. Incrementing the version number is an easier decision to make than explicitly creating a whole new thing. One of the awesome features of Go is how stable the language and standard libs are. Why not expect the same of the community?

It looks like Intel won't be selling a socketed version of this, which means this will be available only in laptops and NUCs. I've had trouble with Linux on NUCs in the past. So, I really hope this goes into a new mac mini.

For the same reason companies make SoCs. It saves money. Intel's idea with EMIB (multiple dies in one package) is to save money by using older semiconductor process for things such as the southbridge (ex: USB) that don't need the latest and most expensive process. This way, they'll also get more value from their investment in previous process nodes.

Routing HBM to the GPU using PCB traces is expensive, and in the low-to-mid end, saving money on PCB and cooling matters. If EMIB is going to be used anyway, why not have the GPU in there as well. With 1024-bit 4GB HBM on package, memory bandwidth won't be a problem, and the i7-8809G will likely be faster than a PS4, which means it'll be good enough for 1080p gaming.

KabyLake was probably chosen because this design was finalized before Coffee Lake. The next iteration will likely have more cores.

I suppose this marks the death of low-end discrete GPUs.

The local newspaper reported that the state government is asking for Aadhaar when distributing free HIV medicine. That seems a lot more problematic.

Jon, there are many here who would very much like to hear what you have to say. If you think it'll get buried, please leave it as a comment to the main thread.

BTW, Jon Blow is the creator of Braid and The Witness. He is also working on Jai, a programming language.

Right. I meant it doesn't support concurrent writes.

I missed limiting the size of user inputs. Will fix it soon.

Thanks! FastCGI is currently not supported. If your shared hosting allows you to run a binary that accepts connections on some port, it should work with Apache as a reverse proxy. I'll add fast cgi soon. It should be easy enough since golang's net/http supports it.

Signup can be disabled. Loading users will need some SQL.

SQLite can handle concurrent reads, but needs to lock the entire DB when writing. Multiple workers shouldn't be a problem per se, but if you need multiple workers to support the traffic, then maybe a client-server db like postgres is a better choice.

Initially, I thought of adding no style at all, like this blog[1]. But, without a max-width, I found it hard to read. I'd love to hear your suggestions. What content do you think should be put to reduce the whitespace?

[1] https://danluu.com/web-bloat/

I'd been working on this on-again off-again for a while after reading Dan Luu's post on page bloat[1].

I'll provide hosting if anyone wants it. That said, ease of deployment was a major consideration right from the start. That's why I chose golang over Django/Rails and decided to offer SQLite as an option to support quick deployment for internal / low traffic sites.

[1] https://danluu.com/web-bloat/

Thanks! Will fix right away.

Images are supported, but it's disabled in the live demo.

Yes - https://groups.goodoldweb.com/

Mali. Not sure about the others.

Games eat a lot of power by rendering this way. So, definitely a concern, and I'd want to see benchmarks before switching from Safari on my macbook.

That said, GPUs are pretty clever about this. A big chunk of power consumption comes from IO. i.e., moving data from the GPU to the off-chip DRAM. Mobile GPUs optimize for static scenes where nothing is changing by keeping hashes of small blocks (say 32x32 pixels) of the frambuffer in on-chip memory. If the hash of a block hasn't changed, they don't bother re-writing that block into the framebuffer. But the GPU is still ends up running the shaders every frame.

The author says ML wasn't used for solving Sudoku. Vision was only used for transducing the image of a sudoku puzzle to a puzzle structure in memory.

That's what I thought too. But the top 100 might be different for different people.

I too have a moderate power difference (-1 on the right and -3 on the left) along with high degree of astigmatism. Two monitors are a lot harder than a single screen. With full correction, eye strain after even an hour of looking at a desktop monitor makes me uncomfortable. So I use lenses that undercorrect while working on the computer.

I really wish AWS would allow users to cap billing. Something that freezes all AWS services if the monthly bill exceeds X would make me a lot more comfortable when experimenting with AWS.

MacBook Air - The keyboard is nice, and the trackpad is small enough that accidental taps are a rarity. Screen is poor though. If you can get a macbook pro 2015, that would be better. But the Air makes a decent budget laptop.

If you're into game dev, you'll need a Windows laptop. Macs are fine for web/app dev.

I remember a time when commenting seemed like a weird idea. Why would someone write on your site instead of on their own site? And then dynamically generated pages and eventually social networks took over. I wonder if the internet would be a better place if everyone had their own websites and RSS/Atom feeds rather than the centralized services we have today.

Won't DNS failover be painfully slow? Some clients ignore small TTL values. I've seen DNS updates taking several hours to propagate.

I thought one of the advantages of multiple zones is that zonal failover can happen with "zero" downtime (this seems to be the case with Amazon RDS).