It looks awesome but I clicked several bits and pieces and still have no idea what they do or what their product is.
Yeah I liked the aesthetic but left the site having no idea what I was even looking at or why I would care.
Why our website looks like an operating system
321–330 of 504 posts
Re: Why our website looks like an operating system
#322What’s it with the definitely not legally required “legally-required Cookie Banner“.
Re: Why our website looks like an operating system
#323Earlier quoted context omitted.
because the OS window manager isn't superior. i have two dozen tmux windows in half a dozen sessions locally. i have shortcut keys to switch between sessions and between windows. i can do that while mixing the terminal with other gui apps. i have yet to find a window manager that lets me group so many terminals into sessions all on the same workspace.
> i have two dozen tmux windows in half a dozen sessions locally. > i have yet to find a window manager that lets me group so many terminals into sessions all on the same workspace. Locally-speaking, I don't really see the point of mixing tmux sessions and tmux windows. I wonder if you mean "sessions" -> tmux windows and "windows" -> tmux panes. What about i3/sway? You can have a tabbed container (functions like tmux…
I don't really see the point of mixing tmux sessions and tmux windows.
sessions let you group windows. i have a group/session for each project/purpose. one session is for all remote connections. one for my personal stuff, diary, etc. one for my hobby. one for personal dev projects, one for client work.
sessions also means that i can connect to tmux from multiple terminal windows. i generally have two windows, one for dev work and one for everything else.
generally i feel that having more than half a dozen windows in a session makes the session unwieldy, harder to navigate, because it becomes more difficult to find the window i am looking for.
which would be the same problem if each was a gui window. try to find your way around 20 gui windows.
Re: Why our website looks like an operating system
#324I've always thought ‘multi-document interfaces’ as we used to call them are an anti-pattern. I have a perfectly good window manager; why does every app need its own incompatible, usually inferior window manager built in? (Mind you on mobile I very much don't have a perfectly good window manager, and indeed can't even open multiple instances of most apps…)
Would you extend that argument to tabbed interfaces as well? Why should browsers support tabs (and an inconsistent interface by each vendor), when you can just open a new window instead?
One could argue that this affordance should be provided by the OS for a unified experience.
Re: Why our website looks like an operating system
#325Earlier quoted context omitted.
The EU law is fine, the implementation used isn't. But never blame the EU laws for cookie banners; the law does not mandate banners at all, let alone the ones full of dark patterns to nag you into accepting anyway. That's all the industry. The industry could have come up with a standard, a browser add-on, respect a browser setting, etc but they chose the most annoying one to pester you, the user.
GDPR requires informed consent before collecting data. It's a wonder we don't have to force everyone through an interstitial consent page.
Yes, this sounds good. This sounds like something desirable. I mean, this is the expectation literally everywhere else so... why not the web?
Also, data collection is fully a choice. You can always choose not to. I've built websites with logins and everything and guess what - no cookie banners necessary. Just don't collect data you don't need.
Re: Why our website looks like an operating system
#326Almost perfect. Inspirational. It just needed to create a little box you can drag around when you click on nothing, like OS desktops have. So here's the snippet to do that, toss this in the console and live the dream: (() => { let startX, startY, box, dragging = false; const style = document.createElement('style'); style.textContent = ` .___selection-box { position: absolute; pointer-events: none; border: 1px dashed…
I just wanted to say, this is a very nice example of clean vanilla JavaScript. Well done!
Re: Why our website looks like an operating system
#327Trying to look at the changelog and the roadmap, and what a spectacularly shitty way this was made.
A progress bar that never seems to finish loading, and restarts whenever you go back to the page, and then suddenly after navigating around and going back to the same page, I get a slow loading html table without any progress indication.
What a great way to really piss off users.
Re: Why our website looks like an operating system
#328Earlier quoted context omitted.
That's not how the process works.
GDPR has nothing to do with cookie banners first of all. Also, literally how the process works is, any citizen of an EU country files a complaint, and you’re suddenly at risk for millions in fines and have to prove compliance to an incompetent non-technical person to stop the inquiries. It’s easier to throw up a banner, hence why most lawyers recommend this regardless of what you’re doing.
> Also, literally how the process works is
It literally doesn't work like that
> any citizen of an EU country files a complaint, and you’re suddenly at risk for millions in fines
Of course you're not at risk for millions of fines because that's not how the process works.
If the relevant agency gets off its ass and decides to actually work on the complaint (very highly unlikely, unfortunately), they will first contact you and ask you to remedy the situation within some time frame (usually quite generous).
If you don't do that, they contact you again and tell you you might be fined for not doing what you're asked.
The only way for you to risk millions is to repeatedly knowingly violate the regulation.
> It’s easier to throw up a banner, hence why most lawyers
Ah yes. The famously competent technical people, those lawyers.
Re: Why our website looks like an operating system
#329Earlier quoted context omitted.
The 'selling of data' is separate of course, but the banners do nothing to actually ensure that they aren't collecting data you don't know about. They're honor system, which is dumb when you could have browsers not send that data back without opt-in. In other words, of course Facebook knows you like bacon if you've followed 5 bacon fan pages and joined a bacon lovers group, and they could sell that fact. But without…
> They're honor system, which is dumb when you could have browsers not send that data back without opt-in. Given that there is no objective way to differentiate between functional and tracking cookies, your "technical" solution would also boil down to honoring marking certain cookies as such by the website owner, effectively being the same as what we have today. (Though I do agree that the UX would be nicer this way)
We don't need the functional/tracking cookie split - the law already thought of this.
If you're using functional cookies, you don't have to ask. If you're still asking, you're just wasting your time.
The reason every website asks is because:
1. They're stupid and don't even bother to preliminarily research the laws they comply with.
2. They actually are tracking you.
Ultimately if you're using something like Google Analytics, then yeah you probably do need a banner. Even if it's just a blog.
Great, so then don't do that.
Re: Why our website looks like an operating system
#330[dead]