Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can't even name and shame because there is no shame, it's like this is every city big and small.

>https://tech-insider.org/discord-electron-rust-gpui-rebuild-...

Even so.. The fact that we are celebrating that a chat app only uses 300MB ram at launch instead of 1GB seems absolutely ludicrous to me

The early versions of Skype used about 30MB RAM while in a video call and by the early 2000s standards it was bloatware. Before that we used WebEx in the 90s which was a browser ActiveX or Java applet and RAM use was about 6MB in a video call. In the early / mid 90s I used CU-SeeMe for video calls and its RAM footprint was just over 2MB on Mac System 7

Something has clearly gone very wrong in the software development process in the last 2-3 decades and while Im encouraged to see that some people are interested in reversing that trend I still find the resource wastage has me shaking my head sometimes


Fun anecdote: When I was in college, my dad read an article in the Wall Street Journal about Turbo Pascal, so he bought me a copy for my birthday. That was version 1. I stuck with TP through grad school and a little bit beyond. It seemed like there wasn't anything it couldn't do. Some of my hardware hacking adventures even required inline assembly. Some of the version bumps were really timely, such as a new compiler that created stand-alone executables. I was extremely lucky that the original TP ran on my non-PC-compatible MS-DOS machine, a Sanyo MBC550.

My graduate advisor had Microsoft FORTRAN, and I tried it out. It was a monstrosity. The compiler and linker had to be on separate floppies, and took eons. My advisor admitted that he had largely switched to BASIC.


This is just another justification piece to blame millenials and gen z for the economy.

How about some real journalism about how propping up the economy through money printing has destroyed opportunity for the current working generation which has led them to these types of behaviors?


There's a difference between coding and programming. Coding itself is not hard — like when you use some framework to build another form on an e-commerce site. But programming itself is harder, since it means you need good knowledge in some area to be really good. Even in the era of agents, real programming is still needed, because AI knows a lot, but asking the right questions or thinking about architecture is still your job.

> If all of this money went into the capital markets instead

Money is neither created nor destroyed (in zero-sum games or otherwise). The real concern here is that, for many people, paid employment simply doesn't look like a viable way to earn a living anymore, so they feel the need to play high-risk, high-reward games in the first place.

If your job is at most paying half of what you need to lead the life you want to live (and that, in many cases, your parents have been able to afford working the same job just fine), suddenly betting on a game that pays double or nothing doesn't seem so irrational anymore.


Real talk. Maybe don't even headline/initially mention that it's something you run or administer (even though you're proud of it).

One can argue that Chomsky's existence has done far more to bring the field forward than to hold it back, even if one only looks at how people have been prompted to challenge Chomsky's views.

> This is wildly wrong

You’re right. I’ve been experimenting with Monaco lots lately and could have sworn it used a canvas. But it doesn’t.

> 2D canvas is consistently slower than letting the browser handle the rendering, so long as you avoid making the DOM too complex, and possibly monitor the viewport and only keep some of the content in the DOM at a time (though for most applications it’s somewhere between harmful and not useful, and it definitely adds a lot of complexity).

Interesting. I’ve found the reverse to be true. But it sounds like this is human error on my part. (probably doesn’t help that I’ve had more experience building high performance GPU applications in Dx, SDL, and similar than I have building high performance web apps.

Thanks for the correction.

> Why on earth would you build with web technology, if you’re then going to use canvas? I can’t immediately think of any that match your description (though I have no doubt that in-browser ones using canvas exist).

You answered your own question.

And I do know of at least one written using the canvas. Because I wrote it. I’m now interested in how others work though.


Your attempts at misdirection are unavailing.

Making it so they aren't in the pool of errors that can be made. I want to be able to type swear words, but I don't want profanity to come out when I try to swipe "duck". Socially, emotionally, and politically loaded phrases make sense to require a bit more care for.

That is a general answer to your question. It is not a specific defense of the particular word list in question. But I can say I've been surprised a few times about what I accidentally swiped on Android. Bitch isn't swipable but I have "bitchiest" readily available, for instance.


I thought this was interesting, from Discord announcement posts:

>Quick update. The U.S. government raised concerns about the game and Steam has paused the release. March 1st is off the table for now. Will keep you posted.

> Update on the Steam situation. The U.S. Department of Commerce raised concerns with Steam that the game could possibly violate some export control laws. So Steam paused the release.

I've researched every law they cited and they definitely don't apply. No video game has ever been subject to these regulations. Microsoft classifies all their games as unrestricted. The physics in my game are intentionally wrong because it's 2D and everything in it comes from Wikipedia and textbooks.

> I'm applying for a formal classification from the Department of Commerce but I've also sent Steam a detailed explanation of exactly how I'm not in violation of any export law. Hopefully they review it and restore the release. If they need the formal classification first it could take a few months.

Couple of months later:

> GOOD NEWS! I have gotten my classification of EAR99 which just means its unrestricted. So we are back on for release!!!!!


On its own? Of course not. Collusion is much more specific a term than that.

I ran a small PC lab at a university for a while and we used PC-Rdist. It was magical!

You could have different templates that all built off of the same base which made switching between different specialized classes in the lab super easy.


  > More than a quarter of Gen Z and millennials surveyed together by Global Strategy Group said they participated in prediction markets, versus 10% of Gen X and just 2% of baby boomers.
This statement borders on lying. At the least it’s extremely misleading framing not supported by their own link.

The 25% of “prediction market” users are entirely doing sports gambling. Two different things that the gambling market desperately wants everyone to confuse.

BS article, do not read.


You need someone willing to defend your argument in court. Someone who knows the process. Someone who knows the particular attitudes of the audience being addressed (judge, jury.)

That’s what the lawyer is for. Most simple things, especially where the law and your case are clear, can be handled by someone without a lawyer. It’s the other stuff where you need the lawyer.


>A DSL needs it clear the minimum bar of “why is this not just using a real programming language?”.

No, a DSL only needs to be better than the language itself to write a layout in. UI is a whole different beast than anything else, where deep nesting is common, layouts flow in many ways, and more. Rust is simply not appropriate to make that pleasant.

Take a simple layout like you'd declare it in Kotlin using Compose:

    @Composable
    fun GreetingScreen(title: String, onBack: () -> Unit) {
        var count by remember { mutableStateOf(0) }
        val scope = rememberCoroutineScope()

        Column(Modifier.fillMaxSize()) {
            Surface(Modifier.weight(1f)) {
                 Text("Count: $count", style = TextStyles.h1)
            }

            Button(onClick = onBack) {
                 Button(onClick = { count++ }) { Text("+1") }
                 Button(onClick = {
                    scope.launch {
                        delay(1000)
                        count++
                    }
                 }) { Text("+1 later") }
            }
        }
    }

Kotlin naturally has trailing lambdas, method references, has the advantage of being a GC'd language so memory management is out the window.

In pure rust ?

    pub fn counter_screen(ui: &mut Composer, on_back: Rc<dyn Fn()>) {
        let count = remember(ui, || 0_i32);

        column(ui, Modifier::new().fill_max_size(), {
            let count = count.clone();
            let on_back = Rc::clone(&on_back);
            move |ui, col| {
                surface(ui, Modifier::new().weight(col, 1.0), {
                    let count = count.clone();
                    move |ui| {
                        let label = format!("Count: {}", *count.lock().unwrap());
                        text(ui, TextProps {
                            value: &label,
                            style: Some(&TextStyles::H1),
                            ..Default::default()
                        });
                    }
                });

                row(ui, Modifier::new(), {
                    let count = count.clone();
                    move |ui, _row| {
                        button(ui, ButtonProps {
                            on_click: {
                                let count = count.clone();
                                move || count.update(|n| *n += 1)
                            },
                            enabled: true,
                            modifier: Modifier::new(),
                        }, |ui| text(ui, TextProps { value: "+1", ..Default::default() }));

                        button(ui, ButtonProps {
                            on_click: {
                                let count = count.clone();
                                move || {
                                    let count = count.clone();
                                    spawn(async move {
                                        sleep(Duration::from_secs(1)).await;
                                        count.update(|n| *n += 1);
                                    });
                                }
                            },
                            enabled: true,
                            modifier: Modifier::new(),
                        }, |ui| text(ui, TextProps { value: "+1 later", ..Default::default() }));
                }
            });

            button(ui, ButtonProps {
                on_click: { let on_back = Rc::clone(&on_back); move || on_back() },
                enabled: true,
                modifier: Modifier::new(),
            }, |ui| text(ui, TextProps { value: "Go back", ..Default::default() }));
        }
    });
}

What a delicious piece of trash. Since you've said no macros, you're carrying an additional variable everywhere (Composer is a Compose system, but you have the same thing in every UI library that does the same. Call it Context, whatever you want). You have shitty lambdas that need to pass the scope too (because Modifier.weight() only works on a ColumnScope). You have no named parameters, and the only way you would would be crap like having a ButtonProps struct. You have impl Fn() + 'static written in your code. And then if you start to want to do some actual work like "clicking on the button increases a counter", you're suddenly spamming Arc::clone, |move| Rc's everywhere in your code because Rust is simply not a good language for UIs.

(And if you want to go the old school way of simply managing yourself a widget tree, good luck, not only is it always full of bugs, it's also an unmaintainable garbage fire.)

Clojure is not a good language for DSLs either, and the post you've linked is just jerking itself off saying "look i can convert some clojure into the exact bash equivalent by only changing one thing" when it's the exact reason why every single clojure project ends up reimplementing the wheel twelves times and is a piece of shit unmaintainable kludge of whatever code the local genius wanted to commit in this morning. Good languages have constraints.

So yes: DSLs _always_ offer a better alternative. QML is a good DSL, and using Javascript is not the reason why.


All I can say is archives, pistols only, 4 controllers and some friends.

"A former spyware maker, who was previously banned from the surveillance industry after a data breach at his company exposed people's sensitive data, now faces a second U.S. federal enforcement action after allegedly running a government impersonation scheme that purported to offer passports and visas to consumers."

We had these in the 80s:

https://en.wikipedia.org/wiki/Casio_Film_Card_calculators

I don't think it's too wild to expect Linux to run in this form factor, 40 years later.


I've already something similar - https://city.scaleupcto.com - I have a v2 with multiplater which I need to finish off, exactly as you describe!

All of the political representatives are landlords and they control supply through the legal system.

But there's just no way.

> Any author who uses such a website strategy gets insta-perma-banned by me.

can we make this into a copypasta? lol


Is Matrix a good solution for internal company communication? Or is it better to go the way of "industry standard" like slack?

This is very cool, I wish they would make quality+time comparisons between the various quantisations though

> Sure, I could say that my incentive is the interest rate, but my alternative is zero risk.

The risk of missed purchases isn't zero and the risk of missing investment profits isn't zero either. From motivational point of view, inflation and deflation aren't different, they're the same thing in a mirror image.

Deflation is rare as hen's teeth, harmless and extremely easy to fix. Inflation, on the other hand, is the most corrupt economic phenomenon by far, it's hard to fix and it has ruined numerous economies, caused wars, destruction and famines.

> Debt has something of a bad reputation and obviously it can be overused and abused, but it’s also something that helps the efficiency of economies.

This is a strawman, nobody said debt as such was bad. However, since you started, let me correct you - as it is, debt not only "can be overused and abused" - it is routinely abused and overused and inflation is a huge part of it.


You're sucking the spirit out of this board

There will be progress, but progress vs money relation is non-linear. Low-hanging fruits got picked early, so dumping another $100B might bring zero results or only small improvments.

Dramatic improvements in battery capacity and durability require big material science breakthrough and those may come from unexpected directions (i.e. optimizing ICE engines, as mentioned.)


I wrote the same blog post in 2025, here's an update.

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

Search: