stu_k

How does one handle an upgrade to mutators? If a client is running old code then the operation will differ to the server. Obvious answer would be to version them independently: `increment_v1`, `increment_v2`, but wondering if there is a better answer?

Has anyone built a mobile app on top of SQLite that can work offline, but then sync to a server when it gets connectivity? It feels like this could be built with a similar approach to this distributed SQLite, you'd "just" need more robust conflict handling.

Looks great! I've currently use https://contexts.co/ but might switch over for the thumbnails

This also addresses an issue when you transition from black to transparent to emulate a shadow, and end up with a "cliff" where the gradient abruptly changes. You can see this in the tool when you transition from black to white with LRGB. Any of the other color spaces avoid it. Very cool!

Although it technically has cross platform GUI, Flutter has actually reimplemented all the native OS widgets. As soon as the OS changes some look and feel your app will look out of date.

Do you know what effect those changes have in the body?

We currently use wasm on the Adobe XD team for rendering shared prototypes in the browser. It allows us to share C++ rendering code across desktop and web and has been a massive success for us.

The browser support is good enough for our customer base, as it works across all operating systems and mobile devices, and we can fall back for asm.js for IE11.

You might be interested in a tool I wrote to serve .har files called server-replay: https://github.com/Stuk/server-replay

It also allows you to overlay local files, so you can change code while reusing server responses.

Thanks for mentioning Arq, that looks really useful. What are the cons you've found?

"atom" probably includes searches for the particle, not just the editor, so not really fair comparison.

Also "vs code" trends higher than "visual studio code", so take all of these results with a pinch of salt.

System Preferences > Keyboard > Customize Touch Bar (at bottom). Drag off buttons you don't want, drag on buttons you do.

Not 5 seconds, but probably less than a minute.

It's in the article:

"These switches to generic medical and psychotropic medications have from time to time caused an increase in reported adverse events, and this is likely to be due to negative attitudes towards generic medicines rather than pharmacological differences between the branded and generic versions of the medication.

This phenomenon is known as the nocebo effect"

Flutter looked great, until I realised that they were re-implementing all the OS controls themselves. For example: https://github.com/flutter/flutter/blob/1db5d66932b873e17c8c...

This is the kind of thing that leads to an "uncanny valley" app, where things feel slightly off, or they look good until the OS changes something and Flutter doesn't keep up.

Citymapper[1] will do that to a certain extent and it’s pretty good, especially with docked bikes.

I wish I could tell it I like walking more than catching a connecting bus, so I’m occasionally working on a side project to allow custom routes for common commutes.

[1] https://citymapper.com

Interesting project!

Is there a writeup on how you architected the project to share 99% of code? I'd be really interested in reading that! From a skim it looks like React + React Native.

Some developers might see this as a good move for them. I don't think it is.

It might be a good move for developers in the short term but it’s a bad move for developers and the web in the long term. We need to keep the web APIs vendor neutral so that one company cannot take control of the future of the web, and move it to benefit only themselves.

The number of barely-standardised APIs they’re adding to Chrome is astounding. It's great to push the web forward, but the fact that product teams at Google have a direct connection to the Chrome team allows them to prioritise the features that benefit their web apps the most.

If the web is going to become Chrome (and sadly it looks like it might), then Chrome needs be moved to a foundation that's outside the control of one company.

Lots of interesting bits in here, and some parts very prescient. The more interesting thoughts to me were near the end: “throw-away workers”, and the last quote on “truth”.

There are very few individually maintained OSS projects that would generate enough money from donations.

Henry Zhu, who maintains the massively popular Babel transpiler, only gets $2200/month in donations

https://www.patreon.com/henryzhu

This is great, I love rush hour.

Is there an web based version of the game where I can try some of these generated puzzles?

Except that rendering everything to canvas is not accessible to people with certain disabilities.

Also mentioned recently here https://news.ycombinator.com/item?id=16347216

Vegetarian means you don't eat animals, not that you don't eat GMOs...

I'm confused, how would the above help with a typosquatting package? The issue here is that `crossenv` is malicious, and `cross-env` isn't. The signatures would all be ok in both cases.

The title is slightly misleading. This just looks like an alternative way to run Cucumber, not a complete alternative to Selenium.

Thanks for the mention but I only created JSZip[0], the library that powers the zip/unzip of js-xlsx[1], but not js-xlsx itself!

[0] https://github.com/Stuk/jszip [1] https://github.com/SheetJS/js-xlsx

Speaking of which, can anyone recommend a good VPN provider?

You run Browserify to bundle your modules offline, and then embed that bundle. With require1k you just embed the script and use one of the API methods to load your main module and everything is downloaded as needed. They are two different approaches.

require1k has a limited feature set (due to its size), creates a lot of http requests and is really suited for a small prototyping where you don't want to set up Browserify's build process. Browserify is what you should actually be using for production sites.

If anyone has any questions, ask away!

Submitting files with this form encoding is of course going to have the base64 overhead, but otherwise this looks great!

I can see that this approach might be viewed with a lot of suspicion, but this gels with a lot of problems we saw while building the MontageJS framework.

CSS is global, and it is a big problem to manage while building a large web app (which of course Facebook is). I think everyone building a large site or app has come across a bug where a CSS rule is unintentionally overriding another. They are a pain to track down and almost impossible to prevent.

I haven't played with this approach (as it was only talked about today!) but I think it's on the right track. The only thing I would like to see is the "CSS" put into its own module and required into the component JS file. Not only would this maintain the separation of style and markup, but also make it more approachable for those CSS experts coming from the current way of doing things.

I'm really looking forward to seeing how this progresses.

This is a great idea. I do wonder how many people taking the southbound shuttle on Fridays or Saturdays will be drunk!