I have a strong suspicion this isn't limited to Baltimore. Not sure what they expected when they show officers they can get away with just about anything with little more than a slap on the wrist.
And what kind of repairs are that? As a software developer I don't understand what equipment is failure needs software change. Software don't wear and tear. Hardware does.
> "If a farmer bought the tractor, he should be able to do whatever he wants with it," Kevin Kenney, a farmer and right-to-repair advocate in Nebraska, told me. "You want to replace a transmission and you take it to an independent mechanic—he can put in the new transmission but the tractor can't drive out of the shop. Deere charges $230, plus $130 an hour for a technician to drive out and plug a connector into their USB port to authorize the part."
I don't know about tractors, but I do know some examples from cars that might be relevant.
The security system on some cars talks to keys electronically, and relies on a chain of trust between components. Kinda makes sense - you don't want a thief to be able to reach under the car, plug into a cable and issue the unlock doors command. The practical upshot of this is replacement doors won't unlock the central locking, unless you have them installed by the stealership. This happened to my father, when someone reversed into his car in a car park and dented his passenger side door.
The go-to example used by car manufacturers when they want to advocate for this lock-in is 'counterfeit' airbags. You can google and find reports of this sort of thing - authentic-looking airbags selling for $200 when the manufacturer charges $400. Some of them aren't as good as manufacturers' parts - and short of discharging the airbag, buyers have no way to check their quality.
The car manufacturers would then argue that unscrupulous second hand car salesmen might not tell you the car had a non-original airbag.
Looking to the future, in some articles about self-driving cars you'll hear that cars of the future will communicate with one another, allowing drafting between cars at highway speeds, and intersections without traffic lights [1]. If such a system comes to exist, I sure hope bad actors wouldn't be able to remotely crash my car - and I'm sure car manufacturers will use this as an excuse to lock out owner and third party repairs.
All software ships with bugs. Some of them cause real problems, and are patched in the next firmware rev. Farmers (rightfully) resent being held over a barrel in both time and money for fixes that should be part of already owning the machine. For example, if Ford discovers a flaw in their cars' ABS code that is recall-worthy, that's what happens, and Ford, not the customer, foots the bill.
None of them have made a lot of money, but one is still generating a small amount. Guess which. Hint: Income is not proportional with the shinyness of the technology stack
Do YOU know the difference? Would it hurt to be more concrete? I'm going to venture a guess based on my assumptions, which are probably wrong, but then we can at least start a discussion:
-VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another
-VS Code doesn't support runtime debugging (breakpoints)
-VS Code doesn't have a visual editor
-VS Code doesn't have memory or performance profiling tools
-VS Code doesn't have source control integration
-VS Code doesn't have an integrated build tool (MSBuild)
> VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another
F2 "Rename Symbol" (works on Go with gorename). Can't imagine using Roslyn doesn't (or won't soon enough) allow the same. From the readme:
Great C# editing support, including Syntax Highlighting, IntelliSense, Go to Definition, Find All References, etc.
> VS Code doesn't support runtime debugging (breakpoints)
It does. CMD+Shift+D goes to the Debug sidebar. CMD+Shift+P Debug shows a bunch of commands. From the readme:
Debugging support for .NET Core (CoreCLR). NOTE: Mono and Desktop CLR debugging is not supported.
> VS Code doesn't have source control integration
CMD+Shift+P git whatevs is used daily here as well as Ctrl+Shift+G for the git sidebar that can show (editable) diffs. Both the gutter and scroll bar are annotated with git info.
> VS Code doesn't have an integrated build tool (MSBuild)
MSBuild comes with .Net Core and is (probably) invoked with the language-agnostic CMD+Shift+B (run build task). C# ext may have more.
> VS Code doesn't have NPM or Nuget integration
There are both NPM and NuGet extensions available.
Now of course if what you want is all of this nicely packaged and wrapped in a GUI, well, obviously VS Code is not an IDE (as VS is) but that's precisely its value proposition.
I stands for "Integrated" in IDE. Project generation, code inspection, source control, database access, refactoring, debugging, test running, etc are integrated.
Visual Studio Code generates project via third party tool - dotnet new. Refactoring, code completion is done via third party tool - Roslyn (?). Etc. It's an editor with plugins. Unlike Visual Studio or Jetbrains Rider.
It would not hurt, but it would be an arduous and unnecessary task. Most people know the difference, and if you do not, you can read the Wikipedia article on IDE. There is no need to have a discussion on the differences, it is not remotely interesting or fruitful.
I guess what annoyed me was that after thebeardedone said he'd googled for 15 minutes trying to figure out the difference between VS Code and VS, 4 answers to his post gave absolutely no clarification as to what the differences were, including yours. If you look up the definition of an IDE on Wikipedia, VS Code falls into that category.
Depends on the type of rental, I guess. If you're looking for long-term rentals (years), the process is probably much similar than if you're looking for seasonal or shorter-term rentals.
