A lot of negativity about OSS is deserved, and doesn't necessarily come from supporters of proprietary software, but for long-time OSS users and programmers, who want it to be better.
But many OSS programs are awesome, and OBS is one of them.
I believe a lot of negativity comes from people who believed the OSS preachers "come come, you don't need that proprietary crap, we have everything free and better"
And then most people are in for a surprise, that usually the above is only true in theory. But in reality there are driver issues, missing firmware, outdated repositories, broken updates ... critical missing features and in general a need to understand technical details with no polished UI.
And speaking of, with OBS I really liked the UI to just get started, but performance/quality of produced video was way worse for me, then simple screencapture with ffmpeg.
It was very heartening to have this experience! I tried to refrain from harboring overly positive or negative expectations while setting this up and am quite content with how it turned out (especially since every part of this stack can run on Linux; this morning, I swapped out the gaming desktop part of this setup out for my Linux dev laptop + eGPU just for fun, and it all works identically).
What's the negativity? Anything wrong with OBS in particular? I haven't used it in a while, but recently saw DHH saying it's awful. I reckon that's the usual Twitter hyperbole/rhetoric that attracts attention, so just wondering.
That's not what he said. OBS decided to not support streaming to Rumble for political reasons. So Omarchy is gonna ship a leaner alternative soon-ish, that's all.
Must be quite comfy to live in such a simplistic reality. Imagine not having to think through all the complexity of life all the time by just crying fascism whenever people disagree with you.
Was envious for a second there. Then I was reminded that I quite enjoy thinking.
This is disingenuous. You chose to word it in a ridiculous way: "crying fascism whenever people disagree with you". If you enjoy thinking, please think a bit more and be more charitable. Maybe it's not "crying" at all? Maybe it's not because of a simple disagreement?
Is there any other reason to use this distro other than signal political alignment? I looked into it a few months ago without even being aware of the political controversy surrounding it (I was curious about the whole "Agentic Linux" angle) and all I found was a poorly configured Arch Linux install with some rather crappy bash scripts on top.
Well, ok, I think there's another use case which is to LARP as a Un*x "pro user" without actually having any idea how to properly use a shell.
To be clear I'm accusing the distro to steer people in a certain direction, I'm arguing that it's something that people who already have a certain set of political beliefs will be drawn to.
>That you think it's all about UNIX guru LARP I have to question how many Omarchy users you actually engaged with because I've mostly met humble and friendly folks. YMMV.
I mostly base myself on the tweet wall posted on Omarchy's website, because it features (or featured, back when I looked at it) a bunch of former Mac users patting themselves on the back for being such 1337 h4x0rs for... mainly using a tiling WM, as far as I can tell.
As someone who has been using Linux and tiling WMs for over two decades it's a bit baffling to look at frankly. I guess I'm a bit salty that I missed out on millions of dollars by sharing my config files.
>I've been working a lot on customization and upstreamed some patches and I have no idea what would count as poorly configured.
I obviously haven't surveyed the entire ecosystem but the base scripts shipped with the distro (which I presume are mostly DHH's work) look more like a personal dotfile compendium than something a serious distro would ship. I'm talking about stuff like this: https://github.com/omacom/omarchy/blob/1e859d37cb7fef6ac6874...
That "format-drive" function is particularly entertaining, I think.
This may not be representative of the ecosystem at large, admittedly, but given the huge focus on vibecode/agentic stuff in the marketing, I think this is not an unexpected outcome.
Beyond that, using your own, worse package manager instead of leveraging Arch's existing capabilities (but also still using Arch's packages for some things) is just terrible design.
Is this sarcasm or are you really completely unaware of how ridiculous this statement is when it applies just as much to OBS' decision to restrict where their users can stream to?
I was specifically talking about OBS' decision to restrict where their users can stream to, so I'm not sure what you think it is I'm completely unaware of.
Yes, the guy I responded to is using "intolerance" to describe the users using/wanting rumble.
I responded with heavy sarcasm, because i don't think people who redefine words & describe things in outlandish terms are arguing in good faith, so I prefer to tell them I agree, and restate their outlandish claim.
You're now here to police me based on our other interaction, and your misunderstanding of my positions.
I hate that this whole cluster of beliefs exists, but software on my own computer enforcing what I can and can't do for ideological reason is a bit much.
Unless they just didn't implemented it for whatever reason, but someone else can implement this as an extensions or something. Your software obviously doesn't need to support everything.
The snowflakes rounding up people for holding up signs also think volunteers not actively promoting their views are engaged in civilization ending suppression of speech.
The maga idiots tried to get a TV stations license canceled for legal free speech. They hate free speech with a burning passion. I see them talk all the day of how "it is legal" that people of other faiths build religious structures on their own private property. They hate private property and the right to private property. They hate when foreign companies justly and fairly make better and cheaper products, they hate capitalism.
That's the most frustrating aspect. They act as if we've trampled on their rights, but all we're doing is conserving our own energy and not carrying water for their ideology.
Since when is anyone freely entitled to my time and attention?
> Since when is anyone freely entitled to my time and attention?
Funnily enough the same people say the same when it comes to pronouns and such. The right (if we can call them that) immediately copied, perfected and weaponized all the attention seeking and whining they've seen and complained about.
As far as I can tell, it's the latter option. Rumble has a whole section of their website explaining how to use OBS with it [0]. The complaints seem to be entirely based around Rumble not being available in a drop-down menu [1]. It's kind of pathetic honestly.
I may be completely stupid but these instructions by Rumble either completely unhelpful or something on my end isn't loading content in that site. But if that's the actual instructions to get OBS to stream to Rumble, I get why just upstreaming it would've been user-friendly.
But apparently I'm a fascist for this type of wrongthink.
What's confusing about using RTMP or a virtual camera? It's extremely straightforward. I genuinely do not understand how you could possibly need more instructions than this. Do you want screenshots or something?
Regardless, this just means that Rumble needs better documentation. It's clearly possible and fairly easy.
I think my issue is that I don't know Rumble Studio and expected OBS to be able to stream to it without, thus expecting some rtmp links + auth flow in the docs.
Should be as simple as copy pasting server url + credentials or streaming key. My interpretation is that documentation authors either considered it so simple that it's not worth clarifying or since they are pushing for their own software (rumble studio) they intentionally didn't explain it further to encourage people using their software directly without extra step of OBS.
Once you open corresponding panel in Rumble it shows you all the information you need to copy paste in single place with convenient copy to clipboard buttons.
Platforms with "builtin support" require same amount of configuration minus the server url. But since the server url is provided in the same place as stream key, copy pasting 2 instead of 1 value hardly makes a difference. It probably takes less time to copy server url than trying to find it in dropdown containing 70+ other services.
OBS should just do the maliciously compliant here and add the support but throw a little jab in the drop down menu by labeling it "Rumble - Fascists and lunatics only" or something like that.
It's been years since I needed to use it, but: lack of an undo button. Not being able to undo stuff was very annoying, and felt out of place for an otherwise nice piece of software.
I saw somebody else besides DHH talking about their decision not to accept PRs with AI written code briefly. I believe there’s a Rust fork in progress.
http://chessbook.com/training-games is the direct link, for usual Chessbook users it's still gated behind an early-access flag since I'm still working on the UX of playing the bot.
Had no idea FUTO made Immich, kudos to your great work. Wish I could join the team but my Flutter xp is very much hobbyist only... Best of luck though!
Wanting to incorporate an http server into a C project of mine, the only battle-tested or feature-complete options either allocated dynamic memory UTH without an option to override the allocators, or are too opinionated with the core API, like mandating callbacks for everything. Suprisingly there's no decent (single header) C library that don't have these 2 issues, at least that I could find.
I disagree. Technology is inherently political, and it’s valuable and important to get informed and reminded about the many horrible people that are directly or indirectly tied to any mentioned organizations and projects.
The OpenGOAL project is a project to reverse engineer the Jak and Daxter video games and the custom programming language they were developed in: GOAL.
The long-term objective of the project is to make Jak and Daxter run natively on a PC by decompiling and recompiling it with OpenGOAL, our reverse engineered version of GOAL for x86-64 PCs. We do not host any game assets or copyrighted material from the game – we only host tools for reverse engineering and porting the game. The user must provide a copy of the game to use our tools.
When working on large applications, by far the single most important factor in performance is having simple and understandable code.
Understandable but slow code can be fixed. Incomprehensible code can't, so it either stays slow or gets worked around with caching/async processing/etc.
If you want fast software, you should write the simplest thing that isn't obviously stupidly slow, then measure and see what parts you need to change. Occasionally you need to make pieces less readable to make them faster, but it's going to be 5% of the application, not the whole thing.
This is only true up to some point of skill & complexity. Hotspot optimisation only takes you so far. Eventually you can end up with a program that is fast everywhere but which is still somehow slow at the macro level. Like LLVM.
Truly fast software is made by thinking about data flow from the start. If you use the right data structures, the code takes care of itself.
But this is far beyond Clean Code. The examples in that book are neither readable nor performant. He uses bad data structures and hidden mutation everywhere. In the large, that approach leads to a buggy, fragile mess.
Choosing the right data structure isn't in opposition to making simple, readable code; it's part of it. Nothing over-complicates code more than a bad choice of data structure. If you pick the data structure that simplifies your code the most, the vast majority of the time that is also the right choice for performance.
I disagree with much of the advice in Clean Code, but it has nothing to do with performance. Clean Code is bad because it produces overly-complex unreadable code. The reason that it produces poor performance isn't because the code is too readable; to the contrary, if the code was more readable it would be more obvious that it's using the wrong data structure.
I'm not saying that you shouldn't think about performance from the beginning. I'm saying that you shouldn't sacrifice simplicity and readability for the sake of performance until you are sure it's necessary because those things are rarely in opposition to each other on the macro scale.
Nothing is worse for performance than doing work you don't need to do and unreadable code tends to do a lot of that if it has been actively maintained for more than a year or two.
If you go with simple, straightforward data structures you often get adequate performance at the macro level. In my experience, getting really good performance often involves being clever with data structures. It depends how far you want to push performance.
I’ve done a lot of work optimising text CRDTs. There, the simple data structure is (essentially) a list which contains metadata for each character. But you’re constantly scanning and inserting into the list. You can improve it in two ways: first, make each list item store the metadata for a connected span of characters. Second, use a b-tree for fast insertion. Make the b-tree store aggregate metadata in internal nodes. That gets you orders of magnitude better performance - O(n) per keystroke to O(log n). RLE gets ~10x lower ram utilisation. It’s only the obvious data structure when you’ve thought about the problem a lot. And you have to write your own btree - there are no libraries for this. At least, none I have found.
> I'm saying that you shouldn't sacrifice simplicity and readability for the sake of performance until you are sure it's necessary
It really depends on the domain. If you’re making a note taking app, you probably get good enough performance by doing the obvious thing. If you’re making a browser, database, llm inference engine or 3d game engine, it pays to think about perf from the start. But my impression is that most people on this site aren’t doing that sort of thing.
That seems like a pretty niche problem. There are already numerous high quality browsers, databases, llm inference engines and 3d game engines and only a tiny portion of devs are working on that type of thing.
The vast majority of applications are better off using one of the many high-performance, battle-tested implementations of b-trees that already exist, which, for users of those implementations, is one of the simplest and most commonly used data structures; we just call them databases and filesystems instead of b-trees.
Every rule has exceptions but you should know the rules before you decide to break them. For anyone other than an experienced expert, writing your own b-tree implementation in a production system is an extremely foolish decision (if it's for fun or learning, do whatever you want).
There are already numerous iOS apps and numerous websites. And yet, people keep making more!
I think I broadly agree with your overall point. I’ve just spent a lot of my career working on niche problems like this. And there are a lot of people working on systems software. Windows, Linux, macOS, chrome, postgres, etc don’t write themselves. But unless you move in those circles, you can spend your whole life never interacting with any of those engineers.
> we just call them databases and filesystems instead of b-trees.
The b-trees I’m talking about are in memory. Btrees often outperform other kinds of in memory tree structures (avl, rb, binary, etc) because you get fewer dram memory stalls.
I'm not disagreeing that there are cases where it makes sense to implement a b-tree; I don't think there are any cases where it makes sense to implement a b-tree (in production) as a person who needs beginner-level advice about code organization.
This. I've spent a good chunk of my career on performance work and this idea that you can hotspot optimize stuff after the fact is utterly wrong and the reason why so much of your software sucks battery and runs like crap.
Clean code like approaches have a very real cost for users (even in languages with good optimizers) and is usually unfixable after the fact.
> You're sacrificing end user experience for developer ergonomics.
No. You may be sacrificing end user experience, but it's not guaranteed. You have to examine the system under development to determine which style is appropriate.
If you actually have to process huge numbers of these objects, then yes. But if you don't, if whatever the actual real-world object is trickles in at 10 per second, do you need to worry about performance and cache misses here? You're already going to suffer from cache misses because the processing rate is so low.
So you get to make an engineering choice based on circumstances. If you need high-throughput, use a design that satisfies that requirement but maybe forfeits flexibility and maintainability. If you don't, then you can lean towards a design that forgoes a bit of performance in favor of flexibility and maintainability.
Use your judgement, don't follow any rule blindly whether it comes from Muratori or Martin.