This looks neat! I've never really been in to web development, but I'm curious... is it possible to create a standalone .html file for a browser-delivered app? Like, not just PWA or SPA, but... a single HTML App?
If I had modest amount of data in JSON baked into html, what's the barrier to something interesting, say... implementing a minimal spreadsheet or maybe just a sortable/filterable table?
> This looks neat! I've never really been in to web development, but I'm curious... is it possible to create a standalone .html file for a browser-delivered app? Like, not just PWA or SPA, but... a single HTML App?
Yes, you can include your JavaScript and CSS directly inside the <script> [0] and <style> [1] tags, so you don't need to include any other file. Images like PNG, JPEG, ... can be either embedded with a base64 data URL [2] or an SVG with the SVG tag [3].
> what's the barrier to something interesting, say... implementing a minimal spreadsheet or maybe just a sortable/filterable table?
Well, you could go the easy route and use an already existing JavaScript library for this. Libraries are normally included via a URL, but you can just copy the contents of this library into the script tag as mentioned above.
Otherwise, I think it's manageable to do develop it yourself (sortable/filterable tables) much knowledge, but frontend development can be a PITA very fast
Just joined a team and received an M1 Pro laptop but licensed docker isn't in the budget... tl;dr a bit early to tell, but I think it works.
podman-desktop is pretty rough, but it gave me enough confidence to start using podman generally. podman-mac-helper solved a few docker compatibility problems I had in previous attempts in 2021 and 2022.
It seems like my problems getting started with podman just last week wete mainly due to the abundance of already outdated tutorials. Maybe those who are more active in this space can weigh-in, but fixes and common work arounds documented as recently as 6 months ago aren't necessary an longer? For me, podman works without nearly as much fuss as I remember.
I agree. It doesn't take long to get to the author's thoughts on the most common cause: lack of subject matter expertise. That's cold comfort for those who are working against a tight deadline, though.
I'm not sure what you're missing. I think aggregators are great for a lot of things, but I primarily use it for discovery. I infrequently contribute (like this, I guess?). After discovery, RSS is really convenient to continue consuming that source's content, regardless of its appearance on an aggregator a second time.
Ha! That’s not all that different from my experience. I was going to ask if we’ve collectively given up on arguing against DevOps as a title, role, department, etc.
I love org-babel, but am I alone in thinking it’s probably best-used for well-understood workflows? Prototyping something with org-babel usually forces me to kill emacs when it hangs for any number of reasons–I imagine it’s choking while trying to reformat as a table. I’ve experimented with ob-async, but it seems unreliable so far. I wish emacs really were more like an os and could multitask a bit better.
'publishing' is doing some heavy lifting here... I wonder why the author didn't prefer a .org extension on the file. GitHub does a pretty decent job of displaying org-mode as if it were written in Github flavored markdown.
Never mind! I see that this was committed some 10 years ago now. I'm not sure how long GitHub has been doing org-mode rendering or if this was originally hosted in GitHub.
