I for my part have not migrated to GIT cause i do not need the extra hoops like staging area or syncing whole repos over network. I have always a server at my side and can work with checkout/checkin. This implies a hard requirement at interface definitions, cause people can't just alter them. Seeing people struggle with all the problems introduced with the git way of work I feel there is still a big market for not git. People are introduced to git and stop asking if there isn't something more good to there workfow. Excuse my english please, im a non native speaker
Git is a decentralized version control system. Creating a new project is just a `git init` away.
Of course centralized VCS are less popular. You need to setup a server first then wrangle with the server every time you create a new project -> fewer projects -> fewer users.
Pull request, which is a request to merge changes in a git repository.
Or (not in this case) public relations , which is an interface with how the public views your product, service or company. In this case, copilot adding advertising into git pull requests is bad public relations for Microsoft, but the article author is referring to pull request as PR
So they aren't "burned into silicon" then? The article mentions FPGAs and ASICs but it's a bit vague. I would be surprised if ASICs actually made sense here.
They make sense when you consider that 'on detector' electronics has all sorts of constraints that FPGAs cant compete on: Power, Density, Radiation hardness, Material budget.
Nice Project. One of the benefits of such small boards is the ability to provide a "Hands on" experience. Use your hands to wire, press buttons and turn knobs. Emulating all this is a big thing but it takes away the learning in my eyes. It's like flying drones. It looks cool but gets boring after 10 minutes.
It's still around and up to 6th edition! Catalyst Game hasn't been the best steward of the IP, with the rules still being internally inconsistent and usually needing a lot of house rules to fix.
As a non Rust man, how real are the problems in this article? Does it show up in real word or is it just a edge case? I only program in C17, C++ as C with classes and C#. Anyone can give me a good read what Traits even are?
> As a non Rust man, how real are the problems in this article?
Real, but of more concern to folks designing widely-used libraries than to folks using said libraries.
> Anyone can give me a good read what Traits even are?
You can think of traits as analogous to interfaces in OOP languages (i.e. pure virtual abstract classes in C++ terminology).
They just define a set of methods that types can implement to conform to the trait, and then consumers can treat implementing types as if they were the trait.
The major differences are: traits are implemented outside the actual type implementation, so arbitrary trait implementations can be added after the type has been written (this is why we need coherence), and rust uses traits as compile-time bounds for generics (templates).
Another imprecise analogy would be to see traits as operators.
You decide to define the operator "serde::serialize" for "MyType" but then your are stuck because you can't override or select different operators for "MyType" because only one can exists.
That's a regular yet not super common issue with traits (and this is not exclusive to Rust).
It's quite irritating because you wouldn't expect this from languages with this degree of modularity.
It's by the team that did Horizon EDA, which is very much a "craftsmanship-first" effort. and they've been working on this for some time now. My guess is hardly any.
Is it a team really? Most commits seem to come from one user "carrotindustries". I am really interested in an Open Source CAD application with good UX, this one looks great. But I don't want to spend too much time on an application maintained mostly by a single developer. The risk of it being abandoned is too high.
sounds like you be more open to it if Revise worked as a native app (Tauri) with ability to run it against your own LLM endpoint/keys
this may be something I offer one day, with some kind of one-time license. I can't really make this work without a subscription right now, because it relies on servers I host and LLMs provided by 3rd parties which have metered billing.
reply