Hacker News new | past | comments | ask | show | jobs | submit | foresto's comments login

> 5.1 Soundbar

5.1 typically means surround sound, but a sound bar (as I know it) sits in front of the listener. How does yours do both?


I imagine most soundbars cheat since consumer protection is dead, but they're still better (and more convenient) than two simple speakers.


They use feedback microphones to tune the output to bounce off of the walls. Or at least that’s what they claim.


I have read stories of crows bringing gifts to people who treated them well, and there is an account in this article of two crows who were fed by a person then guarding that person from an aggressive crow.


I think this is reasonable. Plasma 6 recently appeared in Debian Experimental, Qt 6 is already in the Stable branch, and a new Debian release seems likely in the coming year. I expect the folks managing Ubuntu just want to make sure their non-Debian stuff is ready for the upstream change.


This means Scintilla (the editor component in Notepad++, Geany, and others) is about 25. It was the foundation of my move away from proprietary editors like Visual SlickEdit, and served me well for more than a few years. I'm glad it's still around.


Same here. I used SciTE and Notepad++ way back in the day, probably 20-ish years ago. They were my first taste of useful light-ish weight text editors (with more features than plain old Notepad). Since then I no longer use windows as my daily driver and ended up settling on Vim, but I'm forever indebted to both SciTE and Notepad++ for opening my eyes.


Me, too! Use mostly Jetbrains these days, but we've been standing up some windows servers, and putting NPP on them - which reminded me of Scintilla: wrote my own turbo-charged IDE on top of it ~22 years ago. That secret sauce led to lots of work.


There is. At least two, actually.

1. Allow community-hosted servers, as were common 20 years ago. These can be moderated with greater attention than a massive global server, and tend to eject cheaters quickly.

2. Server-side analysis. This is arguably more expensive to implement than forcing every player to accept a rootkit, but machine learning might reduce the cost. Moreover, it is more effective in at least one dimension: it can't be circumvented* like a rootkit can.

* https://www.youtube.com/watch?v=RwzIq04vd0M


> What is native on Linux? Gtk, Qt, Motif (lol)?

Linux is not something that encompasses a GUI, so this is a misguided way to frame the underlying concern. One might as well ask what toolkit is native on smartphones, or what language is natively spoken by humans.

We should instead ask what is native on Plasma, or on GNOME.

"Oh, bother. That would mean I have to think of four things instead of three."

Well, yes, Pooh. But the things that make them different are the things that make them, them.


Ok but this is in response to this:

"Just build native UIs. I don't know why cross platform UI has been such a hobbyhorse for so many for so long: it's a stupid idea."

The stupid idea is thinking that building native UIs is targeting a clean, non-moving target and implying it is not astronomically harder than doing something cross platform that is between mediocre and good enough for everybody.

Whenever someone says “just do native” it always turns out they have a cockamamie definition of native, otherwise they would realize the gravity and general unreasonableness of what they were asking.

On a side note, what’s a major* reasonably complex app that isn’t a music player or an IRC client, or something with a simple shell around a canvas like a browser, that targets both Plasma and GNOME natively.

* And whether anyone likes it or not, few people care (as revealed by $$, not bitching on a forum). Blame electron, the web, but even Microsoft cannot even define and maintain a native LnF for their core operating system. As I alluded to, the only small community that cares are those on MacOS and iOS, where there is a HIG that more than 2 people have read and give a shit about, and there is a small market of people that value well integrated Mac apps that will actually spend money. Targeting Win USER32 +/- XAML, Qt, GTK, and AppKit is costly and thankless when you probably could have just used Qt, JavaFX, or Flutter, etc.


I only ever use a half dozen or so public Matrix rooms (I mostly use it for private chat) but my experience in those is nothing like you describe. Unsavory characters occasionally wander in, just as they do on every other public forum I've used, but they are shown to the door and the normal conversation carries on without them.

I wonder how someone must be using the platform, or how they're looking for rooms that might interest them, to get the impression that it's "mostly pedos and far right extremists or other weird anti social characters."


No need to imply hostility like that, it could just have been a factor of when they tried it.


No hostility implied or intended.


These dependency managers are something of a double-edged sword. They avoid a lot of work if your project has a lot of external packages, but they also encourage pulling in lots of external dependencies without much thought. Every one of those, and every one of their sub-dependencies, exposes users of the software to significantly more risk. It's a breeding ground for common vulnerabilities and supply chain attacks.

Partly because of this, I try to avoid external dependencies as much as possible. When I need something that's not built in to the language, I choose in the following order of preference:

1. The standard library and target platform libraries, augmenting any inadequate features with my own extensions if necessary.

2. A very well known, well maintained, and widely used library with few dependencies of its own. Something that could almost be mistaken for #1.

3. Write my own minimal version of what I need, if I can do so with a reasonable level of effort.

4. A lesser-known third-party library, if it appears well maintained, and if I am willing to audit it and every future update to it.

A happy side effect is that a language with no built-in dependency manager is still perfectly viable for me, since it wouldn't be saving me much work anyway.


Well… we can’t save people from themselves. It’s always prudent to ensure the libraries you use are high quality, stable, and well maintained and your list is a good order of reference to live by, in any language.


Also, QML exposes only a fraction of the functionality of the Qt Widgets API.


And vice versa.


More often than not, the contact forms that I encounter impose one or more hassles on the visitor:

Please enable JavaScript. Please allow scripts from these off-site domains to execute on your computer. Please enter a return address hosted by an approved email provider. Please read through all the categories in this drop-down list and select the one that best fits your message. Please fill in these required fields and re-submit the form. Please unblock challenges.cloudflare.com. Please waste your time repeatedly solving annoying puzzles, until our CAPTCHA provider can sufficiently fingerprint you and your browser. Please re-type the text you already entered, because we reset some or all of the form fields due to one of the above complaints.

No thanks. If I'm at a contact page, it is most likely because I have something of value to the site owner, such as potential business or knowledge of something broken on their site. If they expect me to jump through hoops, I won't bother.

In principle, contact forms could be nice enough, just as many web sites could be clear, simple, quick-loading, static pages. In practice, they're generally a burden.

Given that they don't offer much to the visitor even in the best case, I would rather just see an email address.


Yes! It's a plague that's hurting most generic content submissions services.

Most Saas in that area can't see the difference between a freelance portfolio site where you can send work offers and the support form of your local telecom where people will send death threats.

At the end of the day, for the lambda user it's just better to have the forms handled on the same platform as the site (wix, squarespace etc.) than dealing with a generic solution elsewhere.

> email address

On the receiving end, the advantage of the contact form is to map it to something else that email (Google Sheets etc.). Of course you can set an automated email box that will process the incoming mail into something else, but that's just an additional burden.


These hurdles only exist for the 0.0001% of people who deliberately hampered their own web experience in an attempt to reduce ads or tracking.


I gave eight examples (which themselves are an incomplete list). Nitpicking at two of them while ignoring the rest, and projecting fault onto people who experience them, doesn't refute the overall point.

This is worth a read:

https://news.ycombinator.com/newsguidelines.html


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: