Custom domain is nice if you're planning on a real host later, but nowadays you can just use the .localhost domain and skip the whole /etc/hosts editing thing.
tcp6 is a thing though, was created at the same time as ipv6, and it does have ports, along with udp6. But if you really want one ip per stream and just hardwire port 1 or something, it's not like IPv6 does anything to stand in the way of that. Mght have performance issues on some OS's binding thousands of IPs to one interface, but that's on them to fix. Bigger lift would be the APIs that would need to change to manage whole prefixes at a time instead of single IPs.
Monads are popular for side effects because they have an implicit notion of sequencing, so evaluating a monadic expression enforces the sequence of operations. Works out nice for IO and Futures and so on. But List is also a monad, and flatMap (as many other languages call it) doesn't inherently have any side effects at all. Same goes for Maybe/Option (essentially a list of zero or one element), and State (which does take advantage of sequencing).
It's all about getting an intuition for how many things fit the shape:
flatMap :: m a -> (a -> m b) -> m b
Where "flatMap" might have different names in different types. Once you see that pattern in some code, you'll start seeing it in a lot of other places.
Using the dark version of this in IDEA, and had to tone down the keywords and TODO highlights a smidge, but otherwise a really pleasing palette out of the box. I haven't seen a theme I liked this much since Tango.
Okay, I'm keeping the editor theme, but going back to Islands Dark for the UI theme, because there are just too many problems with it, from light-mode dialog titles to dark-on-dark for at least three different UI elements. Color scheme is great, but the dark mode UI needs more attention to detail.
It is an OS-level feature, or at least desktop environment level. Far as I know, it's always been Ctrl-. or Ctrl-; for any GTK app, but Firefox had apparently bound Ctrl-. to something else. So basically, this "added" feature is Firefox getting out of the way of the built-in picker that was already there.
On macOS, it still opens the multi-account container panel, and the emoji picker is still brought up by tapping Fn.
Okay, in that case, I completely misunderstood the issue. If the change is that Firefox now allows the system-level picker to get through instead of blocking the keyboard shortcut, that’s a win.
I thought Firefox was adding its own Emoji-picker UI.
> If the change is that Firefox now allows the system-level picker to get through instead of blocking the keyboard shortcut, that’s a win.
You're almost there :) Firefox now opens the system-level picker for that shortcut, regardless of what global keyboard shortcut you might have configured system-level. So system-level, I have nothing done on "CTRL + .", in Firefox, I have 1Password browser extension triggered by "CTRL + ." so when Firefox version 150 was launched, instead of seeing 1Password when I did the shortcut, it instead showed my system-level emoji picker (which I have no shortcut for), triggered by Firefox.
Why can’t Firefox respect system-level custom keyboard shortcuts? This has been a bug on Mac for like 15 years and they don’t seem to care about it at all, which IMO is ridiculous, it’s core system functionality.
> but Firefox had apparently bound Ctrl-. to something else.
I think up until version 150 it was nothing, as 1Password had `ctrl + .` as the default shortcut for opening up their autocomplete thing, and feels like they wouldn't have chosen that shortcut years ago if Firefox was already using it for something, but maybe I misremember.
Whereas I'm not a great fan of modals for anything where I'd like to refer back to what I'm working on. I guess I'd just prefer some tabs to open as a split by default and close with esc, maybe call them something like "ephemeral tabs"? Basically, steal some ideas from emacs.
And chances are only they know it. If my role has enough cluster access, I can muddle through pretty much any helm chart (with lots of cursing, yes) but it might take me days to set up whatever elaborate bespoke environment and script invocations are needed to replicate the current production setup maybe.
If you're using it after it's dead, you're at risk of further problems of this nature that aren't in the underly nginx reverse proxy but in the code wrapping it.
That's one reason I've always used Traefik as my Ingress (I work mostly with K3S, which uses it by default). Which appears to have had its own security issues too, but it still looks like an implementation issue, not a weakness designed in by the spec.
On EKS I'm using whatever AWS has brewed up to integrate ELB/ALB, but I'll tend to trust it ... though maybe I shouldn't, given all the troubles I have with other integrations like secrets management.
Would love to use Gateway! Every time I spin up a new cluster it goes like this:
- New cluster setup, time to use gateway! Yay!
- Oh crap, like 80% of the helm chart and other existing configurations I need for the softwares I'm trying to deploy STILL doesn't use gateway, this new API that's been out for... like half a decade at least.
- Even core networking things like Istio/Envoy only have limited gateway support compared to ingress
- Sigh. Ingress again.
It's been like this since gateway's inception and every time I check the needle has moved like 2% towards gateway. So I'm looking forward to year 2050 when I can use gateway!
The problem, as CNCF knows, if they pushed Gateway and deprecated ingress the world would revolt due to the amount of work involved to migrate stuff. Therefore, they leave it up to "the people" to do the extra work themselves, who have no incentive to do so since for many usecases it's not materially better.
Metro was a wonderful design for the media player app it was made for. It's great for menu-heavy interactions, not so much for representing stateful things like options and checkboxes and such. Metro isn't the problem, it's trying to shoehorn UIs into it regardless of fit that is.
I don’t agree, but that’s design, people have different opinions. I actually like the Ribbon interface, would have liked it more if they added a search box to it as well but designers hate search boxes.
I don't think there is such a thing as perfect UX and I'm not asking for it. I just want them to stop making it worse.
Seriously tho, why isn't this something that a browser can do? Why can't I just split a tab and say all links from the left tab open in the right? Why not be able to scroll through history as a list of such panes like a smalltalk browser or file explorer on a mac? Maybe even a history tree, able to be forked with a click or two. Tree-style tabs are a baby step toward that, but I'm not seeing much interest out there in actually learning how to run.
KDE's hybrid file / web browser konqueror has had arbitrary tab tiling since 1999 IIRC.. still a gread tool, would just need some love and webextensions support to come back big
> I fondly remember the good old days of 2004 when I first started using Firefox as my main browser and thinking how fresh and lightweight it felt compared to the atrocity that was IE. Firefox, sadly, got bloated over the years. So far, Chrome hasn’t put on the same weight
i occasionally need to compare two tabs. previously that meant that i had to open those two tabs in separate windows and then use window tiling to place them side by side. setting that up was a lot of work. and also it makes switching windows very hard. each side by side view would add two more windows that all need to be cycled through when i switch windows. and don't try to have more than two of those on a workspace. you'll go crazy switching between them.
with the split view it not only becomes very easy, but the split tabs also keep their position among all the other tabs, so i can keep the view permanently without cluttering up my list of windows. currently i have 5 split views in active use. that number is likely to grow...
I think it’s a nice feature. I use it to have designs on one part of the screen and implementation on the other. That way I can jump between “designs | implementation” and “PR | swagger” without managing and resizing tabs. Previously I had to jump between tabs and taking into account the newer screens provide a considerable amount of UI real estate there was screen area to utilize.
I don't understand why browser-makers don't leave window management to the window manager. Split view has been standard in Windows (and probably Linux?) since 2009. I know Mac doesn't really do split windows without additional software, but that's an Apple-being-awkward problem.
just putting windows side by side is not enough. i need to be able to treat those two side by side windows as a unit: see how i use it as an example here: https://news.ycombinator.com/item?id=47913202
no windowmanager anywhere supports that. even tabs could have been solved by window managers. but then we could not get inactive tabs, and the same is true for the tabs in splitview.
if lack of support for inactive tabs are no issue and if you don't use workspaces much, you could use those as a workaround. but that unfortunately at least gnome workspaces are not flexible enough for that. (i'd need dynamic creation of workspaces without automatic destruction, and i'd need gnome to remember which window goes into which workstation. that used to be a feature on some windowmanagers, but i haven't found any that can distinguish multiple windows from the same app.)
reply