Live data from Hacker News

Write code for the web

mrmr.io

271–280 of 364 posts

Re: Write code for the web

#271
That is why we built this open source platform:

https://qbix.com/platform

We bet on the open Web since 2011. We believe Wordpress had huge success for Web 1.0, but for Web 2.0 everything is proprietary. Mastodon is an exception, but it doesn’t go far enough.

This is our vision:

http://laweekly.com/restoring-healthy-communities/

https://qbix.com/ecosystem

Anyway, use it! Let’s opt out and wrest the power from Big Tech!

Re: Write code for the web

#272
post #213

I think this is beautifully written. Giving a lot of context as to "why" they way they are now. I even like it was tagged as "Rant". Which isn't really my standard rant at all. At least not " angry " rant. It also capture a lot of things that I share. Especially post Steve Jobs' Apple. >With Apple I didn’t understand the dynamics. The dynamics is very simple. Once you understand one thing. As a developer, the user us…

> I think this is beautifully written.

Thank you! I'm so happy that what I wrote other have found beautiful to read :)

Re: Write code for the web

#273

Earlier quoted context omitted.

> except for maybe Uber, Google Drive, and games I understand Drive working better as a native app; it needs to be able to provide a virtual filesystem to the OS and do background syncing and such. But why Uber? Uber has (or maybe had) a mobile site that works fine for requesting rides and basically everything the app can do. I don't see what value Uber being a native app adds for the user. The same goes for most mob…

It's interesting because Apple had to be pressured into even allowing native mobile apps. When the iPhone was launched they told everyone to develop web apps.

There was a lot of internal pressure as well, smooth scrolling was such a key product feature that they eventually admitted it was impossible to do in a browser if there was any complexity to the app at all.

Re: Write code for the web

#274

Earlier quoted context omitted.

Nah, the shitty parts of web dev are in basic building blocks other ecosystems handle without a problem. The fact that javascript can run anywhere doesn't mean it needs to have crappy build systems. It doesn't mean it needs to have constant breaking changes and flaky dependencies. CSS is crap for layouts. I've build apps with at least 10 layout systems, and CSS is the worst of all of them.

Correct, but HTML + JS + CSS is the standard we seem to have settled on, and having a globally accepted standard for anything is a unique and historic achievement, let alone for free, fast, and robust global distribution of Turing-complete computation and content delivery. Now we can hope that those building blocks improve over time, but the current situation is so much better than it could have been.

This is beautifully put! I hope more people are able to understand the point you're making, especially how "having a globally accepted standard for anything is a unique and historic achievement".

Re: Write code for the web

#275

Early on, I made the choice to not to invest in learning native mobile development. I focused all my limited time on the web, and I think that, for once, I made the right choice. Today, one can build amazing stuff for the browser. And, in my very humble opinion, the vast majority of apps should've been WebApps — except for maybe Uber, Google Drive, and games. I worked in the journalism business, and, in my country, t…

> except for maybe Uber, Google Drive, and games I understand Drive working better as a native app; it needs to be able to provide a virtual filesystem to the OS and do background syncing and such. But why Uber? Uber has (or maybe had) a mobile site that works fine for requesting rides and basically everything the app can do. I don't see what value Uber being a native app adds for the user. The same goes for most mob…

Uber has the same problem that Death Stranding and Resident Evil have: you can't keep shittons of data cached on-device unless you have it installed as an app and not a webpage. Uber specifically needs to support someone traveling from Sao Paulo, Brazil to Mumbai, India without needing to have more than a whisper of connectivity at their destination. The way you do that is by keeping the UI for every payment provider in the world in the app.

F2P mobile games need to be able to send you notification spam, because they're based around habituation and addiction. You couldn't do that in MobileSafari until very recently[0].

[0] Supposedly. I pinned Google Fi to my homescreen on my iPad, it asked for notification permissions, I see a notification count badge on it's app icon, but it still doesn't actually notify me when I get a text message or call.

Re: Write code for the web

#276

Earlier quoted context omitted.

You're supposed to end your document with a newline. That's a POSIX standard.

I don't mean this as snark, I'm genuinely interested: do you have a phrase I can search for or a link to that? I don't think I've ever heard that before but I would love to start citing it

Me too. Feels like I have an uphill battle with this at $dayjob. Would be nice with some ammo for the showdowns.

Re: Write code for the web

#277

Early on, I made the choice to not to invest in learning native mobile development. I focused all my limited time on the web, and I think that, for once, I made the right choice. Today, one can build amazing stuff for the browser. And, in my very humble opinion, the vast majority of apps should've been WebApps — except for maybe Uber, Google Drive, and games. I worked in the journalism business, and, in my country, t…

> except for maybe Uber, Google Drive, and games I understand Drive working better as a native app; it needs to be able to provide a virtual filesystem to the OS and do background syncing and such. But why Uber? Uber has (or maybe had) a mobile site that works fine for requesting rides and basically everything the app can do. I don't see what value Uber being a native app adds for the user. The same goes for most mob…

Uber's native app and its focus on acting partially like webapp to dynamically download new content based on locality is one of the worst aspects using Uber, and is even worse with PWA.

All it takes is for network connectivity to be a little bit spotty (admittedly, Uber made it work a little bit better these days).

In the past, I've been more than once frustrated to rage from the fact that Uber couldn't just grab my A-GPS position, ping for address and send a short packet to order a car, but it had to download potentially megabytes of promo html before it let me actually do anything useful.

Avoiding it with PWA is afaik even harder (currently looking exactly into making PWA because I don't want to deal with iOS).

Re: Write code for the web

#278
> On the other hand, literally every single workaround I’ve had to write in the recent past in web related code has been due to Safari's princessness.

On a recent project I was working on, I noticed that having a long list of items in an overflow: scroll container would still allow the root page to scroll as far down as the items theoretically would. You could just scroll far past the actual HTML root tag because somewhere on the page I had a long scrollable list.

The catch? I only noticed this on Safari.... and Chrome. Firefox is the only browser that doesn't shit the bed on that page.

I just find it amusing that the most annoying problem I've experienced recently with web dev was not because of Safari's "princessness" (it was doing the exact same thing as Chrome), but just because browser engines have become complex enough to be eldritch gods we just have to pray to and hope.

Finally, parity with the desktop.

Re: Write code for the web

#279
One thing about the web is that GPU compute is still not so straightforward to achieve, and even CPU multithreading has a bit clunky at best. For many kinds of apps, web is really not the right answer for these reasons. If all you need is a UI and some fairly minimal background logic, the web could be just fine, though.

Re: Write code for the web

#280
post #247

>the form factor my mother uses has changed from a laptop to an iPad. But it still satisfies that core value prop. >Let's consider a different context. Even if there were no apps in my phone, I would still buy an iPhone. For myself likely, but most certainly for her. I have been thinking about this since COVID. I recently posted [1] on Apps required for setting up a new Mac. Apart from BitTorrent client, VSCode, a Vi…

Yeah, "everything being in the browser" is probably a big part of the reason I can happily daily-drive a laptop from 2012 with a resolution of 1366x768 and 8gb of RAM (ThinkPad X230 running OpenBSD). All the other non-browser stuff I do is like, coding and terminal stuff (other than gaming, which I have a different machine for).
Post reply on HN