I had a feeling that it is similar to R markdown https://rmarkdown.rstudio.com
R markdown is similar in capacity one can mix R language, but since syntax is Markdown they kept the name.
Uh, what? Dang is an incredible moderator. I sure hope HN won't get any closer to Reddit, the discussions here tend to be much more interesting - if anything, mediocrity is the result of influx of Reddit users to HN.
There is a lot more groupthink and echo chamber behavior on HN compared to Reddit due to the way flagging works. For me, HN is unusable without using showdead and using the active front page so I can see what stories its userbase tried to flag off the normal front page.
You can also say some pretty horrendous things on this site as long as you couch it in modest proposed-esque soft language. If I want to have a non-technical conversation with other human beings, Tildes blows the doors off of HN in the empathy department.
Containers feel like a much more useful feature to me than profiles - I don't wanna open a new window for each website that I want to isolate from my main session, but with containers, it's trivial.
I mostly agree, and I personally just use containers (and heavily!) However, that has not been the case for my spouse. Profiles are important to her in two scenarios:
1. The primary website she uses for grad school (canvas) REQUIRES third party cookies to be enabled for it to work. Containers cannot have different settings here, but profiles can. So she can have a School profile that enables 3rd party cookies and she just uses this profile for Canvas.
2. She likes to keep ALL of her work stuff separate and not have that sync to her personal mobile. So she has Personal Profile (with containers) and a Work Profile (also with containers). The two profiles are themed differently, so it makes it very clear if she is in her "work" browser or "personal" browser.
Firefox's profile management has been a struggle for her (I found creating different application icons for each profile worked best), and I am very excited about the new profile manager!
My personal issue with SPAs is that the experience is often not really better than the old school way, it's just the the issues and failure modes are different. SPAs tend to be slower to load, break platform conventions by re-implementing browser behavior and they're are more stateful, making invalid states harder to recover from.
Personally, unless the interactivity is needed (i.e. web apps, not web pages), I prefer a more basic site where I can be reasonably sure that UI will work the same way as everywhere else, even if it's not as fluid.
I think that's very subjective. SPAs load pretty quickly on a modern network. It's pretty much a non issue unless you are a bit OCD about such things. And I've seen some nice examples of SPAs that are actually quite nice to use. Mostly we're talking about the content of 2 or 3 floppy disks from way back (I'm old enough to have used those). Even back then that wasn't a lot. Many interesting things required multiple floppy disks.
My observation is that people vote with their feet. Including developers. The developers who complain the most about this stuff aren't actually building a whole lot worth talking about.
Anyway, it's hard to break conventions when the convention has actually been SPAs for quite some time now. Most major websites are simply not very old school at this point, to put it mildly. That stopped being good enough a long time ago.
My issue with SPAs is that I very often end up in an incorrect state. I don't know, maybe I'm using a browser wrong? I'm clicking on things, pressing back and forward, and almost daily in some SPA app I get to either a blank screen or some error. I then refresh, and inevitably lose the state, as the URL would likely not match the latest correct state of the app.
Core Front-end Team (we are currently full, check back later)
- Passion for creating delightful and swift user interfaces.
- Proficiency in HTML, CSS, and an understanding that JavaScript can be used sparingly to enhance, not create, product experiences.
- You are comfortable not using any FE frameworks, and rather like to be in full control of the DOM and as close to browser as possible.
Fun fact: At Kagi, we prioritize speed, to the point where all functionalities of Kagi Search (except Stripe checkout and Maps) work perfectly without JavaScript. We see JavaScript as a tool to enhance the UX, not create it.
Also related to the article, PowerShell has PSReadLine, which implements a pretty reasonable text editor, including selection, copy/paste, classic keybindings such as Home/End/Ctrl-arrows, sane multiline command editing, semantic autocomplete and custom actions that can operate on input AST.
Once you get used to having all that, going back to other shells is pretty hard.
reply