317 karma · joined August 28, 2014
> You may stop using Copilot at any time.
But how? Microsoft has shoved it into so many products that I don't see how it's possible, without dropping them alltogether.
- anything with good enough adoption is good enough (unless I'm an SME to judge directly)
- build something with it before considering a switch
- they're similar enough that what I learn in one will transfer to others
- everything sucks compared with 2-3 years from now; switching between "sucks" and "sucks+" will look silly in retrospect
I had this experience with Eve Online back in the day. The optimization limit horseshoes back into the real world.
Case in point: just reading this thread started me learning about discrete event simulation. Damn you Factorio.
Delphi is a neat product, but fuck Embarcadero - their business model is to extract revenue from the long tail of old Borland customers who are locked in for one reason or another, not grow the product.
The basic Windows / Linux versions of the cheapest commercial Ada package only recently dropped to high 4-figures / seat. The equivalent cross-compilers are still $$,$$$.
What do you mean by developer?
Lots of embedded systems and industrial automation development is Windows-only, as a random example. Not everything is webdev or mobile. Lots of vertical markets have development environments which are essentially Windows-only.
There were a few decades of research into symbolic AI and expert systems - "Good Old-Fashioned Artificial Intelligence" before the modern deep-learning revolution. Lots of promise, interesting research, and very cool (and esoteric) hardware came out of it, which never found wide application outside the lab. You could pitch it as a sort of analogue to Who Killed the Electric Car? (2006).
In what industry?
For my use, there is a sweet-spot for "models" spanning only a handful of diagrams (5-10) where any drawing software with SysML templates will do. The dedicated modeling tools like EA or Cameo become relevant once you're trying to keep model elements consistent across a large number of diagrams. Draw.io is free so the whole team can use it, and the the lack of model representation keeps diagram count low and not over-specified.
Cool products, btw.
I'm not sold on the idea of capturing an entire design within SysML, but using it instead as a diagram format with defined semantics for situations where group discussion or communication with third-parties calls for some graphical aids. I think as long as you're not trying to make executable models, do code-generation, or replace a formal specification tool like TLA+, there is real value in it. The documentation and training ecosystem around it is pretty decent, as well. The SysML books I've read have all been way more pragmatic and grounded in actual engineering practice of building systems from many components sourced elsewhere, for which design capture is necessarily incomplete.
definition of product applies to current billing period only, Autodesk reserves the right to add or remove functionality without notice
Automotive technical surfacing in CAD is stupid hard, and is a waste of time for the design staff. The clay models are easier to work with in every sense - easier to change, easier to refine, easier to show and discuss, etc. Designers can apply reflective film to the clay which shows reflections much as the finished product would, and can even be painted. The final surfaces are reverse-engineered from scans taken from those clay models.