283 karma · joined July 14, 2014
It looks like a very basic stub project that uses a web library (vweb) to serve a very basic web site that's interpreted from a json file, with a stub for some sort of email subscription functionality.
The vweb library seems like it's not the point of this post…
The unfinished email feature couldn't be it…
No problem with someone posting an "I did a thing" post, but, again, A) what is the thing, and B) what's making people upvote this?
Have I just been misunderstanding how things get on the "front page" of HN all these years?
You’ll hear people say “this game sucks!” Some would say to ignore the haters. I’d say learn from them if you can. Don’t engage the ones that just want to poke fun. But if they have a reason they didn’t like the game, you can learn from that. I see some have already called your game “basic,” which might be fair, but it’s not really very helpful. Flappy Bird was as basic as it gets…
Many will miss the point and say things like “not HN material.” I couldn’t disagree more. You built something! And published it! That’s a big achievement. Whether the game is terrible, good, or great you exercised all the muscles it takes to ship something, and the next release (whether an update to this game or a whole new one) will be a lot easier!
hn_expanscape, what is the actual use-case for this device? You mention day-traders, but what about tiny screens sliding out from behind larger screens swiveling out from behind yet larger screens is helpful? Why is this better than one, much larger screen (i.e. a laptop with a 24" monitor or larger)? Why is there a screen embedded next to the keyboard? Was it just another place to squeeze a screen in, or is there an actual use-case for that? And is that a tiny little screen in the upper left portion of the bezel around what I would normally call the "main" screen? What's that for?
Are there digital nomad day-traders who are even interested in using a laptop in the first place? Where are they that they don't mind carrying this very heavy device around, where they have access to a power outlet to use it?
What is the purpose of the battery, actually? It doesn't sound like it's meant for practical use, since it seems it would last for less than an hour in ideal circumstances. Is it sort of a mobile UPS?
I somehow totally missed the live aspect. That's super exciting (and impressive). And parallel!?!? A WYSIWYG parallel code editor for microcontrollers? How is that not the headline?
I'm glad I asked! This is quite interesting to me now. Thanks for your reply!
But don’t take my word for it: https://css-tricks.com/icon-fonts-vs-svg/
“It all comes down to browser support. If you can go IE 9+ / Android 3+, inline SVG is better at pretty much everything than icon fonts. If you need the deeper browser support, I feel like an inline SVG fallback would be too big of a pain to be worth it (maintaining a PNG copy, inserting an additional element to display PNG version, hiding SVG element… it’s weighty).”
Funny how many people respond "the performance isn't there" or "the tools aren't mature enough" as though THOSE things happen first and then you have a platform. They clearly weren't around for HTML's awkward years.
My first thought looking at that SVG code is "we're better off with what we've got." But then I thought of it as looking inside the component code for a React/Ember/Angular/Vue/Svelte/etc. component and thought maybe it wasn't really that much more complex. And out of the box right now it would be possible to re-use at least the markup with SVG's use tag, which, in combination with HTML templates, could be pretty powerful.
I ignored canvas as an option because: 1) It has inherent accessibility problems (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ca...) 2) It's not and never really could be a markup language (by design), so a declarative format would rely on some library like Flutter and would never truly be a standard. I was wondering what the state of web standards would be if we had gone (or now went) that route.
1) I’m not saying we replace HTML altogether. So if you’re talking about writing an article, sure use HTML (and things like section tags).
2) You can make SVG and HTML equally accessible now with WAI-ARIA roles (https://developer.mozilla.org/en-US/docs/Web/Accessibility/A...).
The author misses half the concern of button layout: target acquisition, or “how long, once I’ve found the button I want to use, does it take to tab to it/move my mouse to it/tap it and how likely am I to miss (and potentially hit a different element/button with potentially frustrating or disastrous results)?”
This OPD site gives you the impression it has some of that data, but the browse section does not inspire much confidence. I would love to be able to see information about responsible sourcing, production practices, employment practices, etc. for everything from food to electronics to clothing.