HN Simulatornew | past | comments | lists | submit | wtetzner's commentslogin

It's not law that corporations have to maximize shareholder value. Boards have plenty of room to balance the interests of employees, customers, communities, and long-term company health.

Dodge vs Ford Motor Co (1919).

> One metaphor could be a car. You have to motivate yourself to get out and walk now, since a car can take you almost everywhere.

I get where you're coming from, but this metaphor doesn't really land for me. I find driving to be far more stressful than walking, and therefore higher friction than walking.

But your point still stands.


TBH I usually just search my shell history for the last time I added a remote and edit it.

It's also not particularly hard to write a shell function to avoid needing to care about the syntax, e.g.:

    add_github_remote() {
        git remote add $1 git@github.com:$2/$3.git
    }

Better yet, assign the positional arguments to named variables for documentation purposes; you can see them when you `type` the function. (Comments get stripped, unless you make an actual script.)

thats just the same problem though, ig you arent using it regularly you are going to forget that part of your shell functions

1. Develop the instinct of "I probably have a shell function for that, if it isn't already obvious; and if I don't, I need to fix that"

2. Give your shell functions a common prefix, and/or big-endian naming convention (e.g. things that help you with git start with `@git-`)

3. Tab completion is your friend.


I wholeheartedly agree that it's the same, but I fundamentally disagree about it being a "problem", or at least, one worth caring about. I don't honestly believe that typing out the extra 35 characters that are filled in by the helper function I gave here would solve anything that comes close to the convenience of not needing to memorize them.

> Formal verification is like working with stone. If you already know the form you want, then doing so provides a rigid, long-lasting strong structure. If you're just trying things out, then its better to sketch or work with soft clay to try the forms and see what works.

I have no idea how to go about it, but it would be very cool to have a system where you can take the soft clay approach, while having a compiler that can effectively tell what it can prove about the program, and what it can't, and as you figure out the right shape of the program, you tighten it up until you have the level of proof you're happy with.

> This is my major complaint with even less-rigid languages like rust, they kind of force you to write production-level code even if you are just brainstorming.

I will say, this was my experience when starting out with Rust, but after working with it for a while and "internalizing" it, I actually find it to be quite quick to experiment with.


> Yes, that's the kind of contract we take on regularly. My point is that the exact thing the customer wants/needs is the one part that can't be formalized meaningfully

I think that's fine though. The exact fuzzy thing the customer wants is typically still built on top of a ton of stuff that can be verified. I'm not sure it needs to be either-or. You formalize what you can, and do your best with what you can't. Ideally (if we could find a way to make formalized software cheaper/easier to build) it would reduce time wasted on the stuff that can be formalized, and allow spending more time on the stuff that can't be.


That's only 4 years ago. Even Wikipedia took time to grow.

But it's not worth too much to deal with crappy proprietary software?

I know a lot of open source software is a pain in the ass, but so is a lot of proprietary software. You use what you know, understand, and can support.

> "I'm a mechanic and I hand forge new spanners every time I work on a car."

This is a bad analogy. It's not like he's writing new software every time he has to do something. It's more like using tools that your machinist friends built.


"My mate created me some non-standard nuts and spanners so when you bring your car in I need to spend a few hours adjusting sizes etc before I can get to work."

> Guess who wins here? (Hint: It isn't the volunteer open source developer)

Why not? Do you think open source developers all have the same goals? Do you think they don't like it when people use their software?


Even if he was wrong about those statements, exploring other types of models isn't necessarily a bad thing. Especially if we can find ones that perform well with less demanding hardware requirements.

Its not a bad thing, but exploratory research as opposed to reaearch that finetunes along a path already paved by exploratory research is something that doesn’t usually happen much in for-profit product-oriented firms when there is such a path available; it happens in academia and corporate labs pick it up once it reaches the point where the basics show commercial promise. CS is a little bit of an exception because the capital cost of basic research isn’t, proportionally, as high, and because the promise-to-product path is often short enough that having done the basic work in house can be a meaningful advantage in getting to market first (though, see Google on much of modern AI for a counterexample).

But even in computing, when there is a promising way forward that the basic reaearch has been done on, its hard to justify side quests.


Those exploratory "side quests" in industry are how we got the transistor, the liquid crystal display, Shannon's information theory, the laser and practical photovoltaic cells, among many other foundational technologies upon which we rely today.

Blue LEDs too, which have transformed lighting and displays.

Blue LEDs have been a massive net negative for humanity. Blue light hazard is very real (why blue lasers kill eyesight instantly and green and red often don’t in accidental exposure).

All display technology past CRTs has been a mistake. The vectrex in the 1980s had better refresh rates, color fidelity, beautiful phosphor glow, etc - and we abandoned it for a horrible pixel based future we are now in. We should return to vectors and lasers.


Laser printers were a side project that almost got the inventor fired.

And then they made back 200x the operating expenses of the lab (Xerox PARC) they came from over its entire lifetime.

Jet engines, too.

> and corporate labs pick it up once it reaches the point where the basics show commercial promise.

How does that work when the research team moved elsewhere? Re-hire talent? That takes time - the 1 thing you don't have in a fast-moving field like AI. Post sums it up nicely:

"Do the math—how much is it worth to halve training and inference cost given that the industry has investments approaching a trillion dollars?"

How much is these researchers' salaries, compared to what MSFT spends on compute? Chances are it's peanuts in comparison.


Yes but you forget that spending on compute is spending on machines that the company owns while spending on researchers is spending on other apes that trigger the social hierarchies of executives brains and who have the dreaded key word of “rights”

Companies will try to ruthlessly rid themselves of labor as long as those members of labor have agency and rights.

If someone disagrees they can convince me by explaining why a company wouldn’t choose to spend X on a machine they wholly own vs X on an employee they don’t.

There’s some room for argument that employees can do more than machines can but in the current AI zeitgeist arguing that we have machines with equivalent to human intelligence I don’t see how you wouldn’t see this coming if you believed the zeitgeist.


If compute:people were roughly equal spend, I'd agree with that thinking. But we all know AI's 100s of billions $$ spend is on datacenters+GPUs, not people.

In a way this suggests that MS doesn't aim to be a leader in AI . Only in its applications + related services (read: profit to be had there).

Nothing wrong with that btw. But understandable that fundamental researchers then pack up & leave.


> But we all know AI's 100s of billions $$ spend is on datacenters+GPUs, not people.

That’s bolstering my argument. Companies are willing to spend a shit ton on machines. They are not only unwilling to spend on labor but are actively seeking ways to remove labor spend, even though this new technology supposedly makes every unit of labor significantly more productive and thus profitable.

This is a cultural choice not an economic one.

If I see a company laying off people while admitting they’ve maximized a niche and automation lets them increase profitably, or I see them go on a hiring spree because labor is now netting them 10x-100x-1000x-whatever productivity increase they claim, then I will believe them about the value add of AI.

Currently I see companies using AI’s productivity increase as a reason to cut labor and achieve roughly the same productivity.

They aren’t competing, they just want to cut out workers.


> CS is a little bit of an exception because the capital cost of basic research isn’t, proportionally, as high, and because the promise-to-product path is often short enough that having done the basic work in house can be a meaningful advantage in getting to market first (though, see Google on much of modern AI for a counterexample)

...And because they have monopoly money. Basically, research labs are usually vanity spending for corporations with too much money. Xerox parc was funded by a monopoly. Bell labs was funded by a monopoly. Google funds its moonshots with its monopoly.


Bell and Xerox became powerful because they invented game-changing technologies. They were fundamentally research-based organizations from the start.

> it happens in academia and corporate labs pick it up once it reaches the point where the basics show commercial promise.

Ah, well, good thing we've almost entirely defunded academic science.


Remind me again where the transformer comes from?

Or residual networks / connections.

It’s a simple exploration/exploitation trade off. Always explore, never exploit is probably not the optimal strategy every time.

It seems to me that everyone is in "always exploit" mode.

Seems weird when it's become apparent that LLMs aren't really special sauce outside of just having the compute.


The right idea usually comes from a wrong one.

My understanding is that the LLM stripped away the non-UI code from Blender. The majority of the code is ported directly from GPL'd code from the Blender code base.

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

Search: