Hacker Newsnew | past | comments | ask | show | jobs | submit | octopoc's commentslogin

.NET standard isn’t the biggest issue with making source generators. You can’t add dependencies to your project, which is an absolutely huge oversight IMO.

You can add dependencies, it's just important, that you also add the dependencies to the project where the source generator is used:

SourceGenerator.csproj:

  <ProjectReference Include="..\Dependency.csproj" />
FinalProject.csproj:

  <ProjectReference Include="..\Dependency.csproj" OutputItemType="Analyzer" ReferenceOutputAssembly="false" />
  <ProjectReference Include="..\SourceGenerator.csproj" OutputItemType="Analyzer" ReferenceOutputAssembly="false" />
And I also recommend to add "<LangVersion>latest</LangVersion>" to SourceGenerator.csproj to use new features like raw string literals.

This is a good summary of the problem with rust I think:

> Pretty much all UI can be modeled as a tree–or more abstractly as a graph. A tree is a natural way to model UI: it makes it easy to compose different components together to build something that is visually complicated. It’s also been one of most common ways to model UI programming since at least the existence of HTML, if not earlier.

> UI in Rust is difficult because it's hard to share data across this component tree without inheritance. Additionally, in a normal UI framework there are all sorts of spots where you need to mutate the element tree, but because of Rust’s mutability rules, this "alter the tree however you want" approach doesn't work.[1]

[1] https://www.warp.dev/blog/why-is-building-a-ui-in-rust-so-ha...


If I’m being charitable that is an oversimplification, and I suppose I should be charitable at Christmas. But the Scrooge in me is screaming that this analysis is deeply flawed.

Rust makes ownership and mutability explicit. Concurrent editing is very dangerous no matter what stack you are using. Rust just doesn’t let you get away with being a cowboy and choosing YOLO as your concurrency model.

Shared mutable state isn’t any harder in Rust than other languages. In fact, writing correct, bug-free and performant code is easier in Rust than almost any other language in common use, because the tooling is there. It’s just that the other compilers let you ship buggy code without complaining.

To the specific example, there are ways of sharing mutable state, or encapsulating changes throughout a UI tree. I’ve written a UI framework in Rust that does this. It is difficult to get right. But this is true of ANY language - the difficulty is intrinsic to the data type, if you actually care about doing it correctly.

That difficulty does not need to be exposed to the user. There are plenty of Rust UI libraries that take react-like lambda updaters, for example.

I still fail to see the connection to garbage collectors.


Yes because the alternative is extinction, any price is worth avoiding that

Seems like SCIP would be a better fit, although not as widely supported by languages I suppose.

It takse long to regen on big codebases, but yes

I really enjoy Junie, I find it working better out of the box than Claude code. I do wish they integrated their amazing refactoring tools into it though.

Zionist Jews wield a lot of political power in the US. It’s difficult/impossible to get elected at the federal level if you don’t support Israel.

Supporting Israel is valuable to Trump because many of his donors are these Zionist Jews.


I think that it's actually the opposite.

I haven't followed in the recent past, but a few years ago, if my memory serves, Netanyahu was largely funded by a group of US Evangelists.

It's not Israel or Zionism controlling the US. It's some subset of US Evangelists using Israel as a puppet for whatever eschatological purpose they have in mind.


Devs should not recommend rewrites until they have a workable plan on how to move forward without a rewrite, so they can compare the costs of rewrite vs. no rewrite.


I believe gp was saying that density is an advantage for fossil fuels. Nobody thinks it’s a disadvantage/problem for fossil fuels.


I send multi line messages all the time and I frequently accidentally hit enter before I’m done. Then I have to rapidly make edits and save them, hoping everyone sees the frequent updates and realizes messages is still a work in progress. There has to be a better way.


Would be nice if anything that supports multiline messages let you toggle into a multiline mode where enter always puts in newlines and a combo like ctrl+enter sends the message.


I've gotten in the habit of typing any long messages in my text editor first and them pasting them into Slack for this exact reason.


When I have a multi line message to send, I always redact and edit it in my favorite text editor, so no accidental send can happen. Plus I have all my shortcuts


How are the Reddit execs right wing? Reddit had a hilariously bad relationship with the trump subreddit, in fact the CEO famously edited user comments in that sub to change them from being critical of him to being critical of the mods[1].

[1] https://techcrunch.com/2016/11/23/reddit-huffman-trump/


He edited comments about himself. It wasn't some conspiracy to push anti trump messaging.


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

Search: