"In 1996, Hejlsberg left Borland and joined Microsoft. One of his first achievements was the J++ programming language and the Windows Foundation Classes; he also became a Microsoft Distinguished Engineer and Technical Fellow. Since 2000, he has been the lead architect of the team developing the C# language. In 2012 Hejlsberg announced a new Microsoft project, TypeScript, a superset of JavaScript."
I can only speculate that lots of skilled Borland developers followed Hejlsberg and participated in creation of C# and later TypeScript.
The story I heard (I worked at Borland briefly in 1999): Microsoft would send a limo to the Borland HQ to pick up engineers for interviews on their lunch breaks. Borland sued, Microsoft settled for many millions, but basically instead of buying their rival outright (for assimilation into the Borg, lol), they just bought the talent. Last I knew Borland had changed names at least twice (Inprise, Embarcadero) and still existed, in some remnant form.
As did Google when Google engineers started leaving for Facebook, and FB when their engineers started leaving for Uber/Lyft/AirBnB/Stripe/Coinbase/etc, and so on. It's pretty much a revolving door now, where many engineers have worked at all these companies and sometimes even come back to their home base.
CA's prohibition against non-competes and the DoJ's lawsuit against anti-poaching agreements is basically what makes Silicon Valley work.
Oh that definitely happened, but we don't have quotes from Google like this:
Prior to joining Google, I set up a meeting on or about November 11, 2004 with Microsoft’s CEO Steve Ballmer to discuss my planned departure….At some point in the conversation Mr. Ballmer said: “Just tell me it’s not Google.” I told him it was Google.
At that point, Mr. Ballmer picked up a chair and threw it across the room hitting a table in his office. Mr. Ballmer then said: “F---ing Eric Schmidt is a f---ing p--sy. I’m going to f---ing bury that guy, I have done it before, and I will do it again. I’m going to f---ing kill Google.”
Borland sold their software division to Embarcadero, which appears to have been a big payday for top execs as they jumped out. However, Embarcadero did do a decent job of keeping the ship afloat and running things, though Delphi got very expensive. Idera then bought Embarcadero, but appears to allow it to have a high level of autonomy.
At some point there was an attempted pivot as well or maybe it was just what Embarcadero always had focused on.
I wasn't yet working in software then I think but there was an interview or paid article or something I think were someone told that the future of software laid not in languages and IDEs but in Software Lifecycle Management.
In a way they were right:
Today all major languages have free and open source implementations and Atlassian and a few others seems to have found larger or smaller sweet spots in what I think is Software Lifecycle Management or something.
That said what could Borland do at that point? It probably felt worse for them to bet the farm but in my opinion it absolutely isn't the most bone headed moveI have seen.
That said: The ads not so long after for "Delphi con" or something similar with large "No toothbrush required", that didn't exactly seem smart to me. I think by then everyone who used their products were grown up serious business programmers.
> At some point there was an attempted pivot as well or maybe it was just what Embarcadero always had focused on. [...] that the future of software laid not in languages and IDEs but in Software Lifecycle Management.
That was after they'd changed their name from Borland to Inprise, before they sold out to Embarcadero. I think that, in contrast to this, Embarcadero still bought them mainly for the IDEs.
> I think that, in contrast to this, Embarcadero still bought them mainly for the IDEs.
Indeed, seems it was the dev tools division Emba bought. Maybe the ALM div is still around. Hm, have I actually heard somewhere they even switched the name or that back from Inprise to Borland, or am I imagining it? Naah, can't be -- 't'would be both too pathetic and too absurd.
I remember I started getting a bunch of emails from an "Embarcadero." I didn't remember subscribing, and the unsubscribe didn't work, so I just wrote a filter to skip the inbox and send them all to spam. I must have subscribed to something from Borland at some point.
Interesting, do they make a similar effort to hire IntelliJ staff? I mean they could offer a much higher sallary than what they would get in Russia. Or is it all due to having the top guy, who is in the know on who-is-who?
"In the past 30 months, Microsoft has hired at least 34 of Borland's top software architects, engineers, and marketing managers", according to a complaint prepared by Wilson Sonsini Goodrich & Rosati. These actions have been undertaken “for wrongful purposes: to acquire Borland confidential information and to inhibit Borland's competitive position,” the filing states.
Borland's lawsuit seeks unspecified financial damages and an immediate end to Microsoft's unfair practice of targeting Borland employees in order to hamper the company's ability to compete. The suit claims that Microsoft's activities are illegal under California Business & Professions Code Section 17200.
> Saying that he "just wants Microsoft to leave us alone," Borland International (BORL) CEO Delbert Yocam today filed a lawsuit against Microsoft (MSFT), claiming that the software giant is hiring away Borland's key employees to put it out of business.
Not really. Borland could have issued attractive stock based retention packages to the employees they wanted to keep, and forced Microsoft to acquire the company or go away.
This was on Borland for not adequately valuing their staff.
Borland was losing over a hundred million in revenue while Microsoft was offering seven figure signing bonuses. There's no way they could have paid more than what MS was, since MS was using their war chest to kill the company.
If they were losing a hundred million in revenue before their best employees were poached then we should thank Microsoft for saving these people‘s careers.
I do almost nothing but develop products. However as product becomes mature I start looking for new things to do. Also maintenance of mature product requires different type of people, not inventors.
Long term this kind of practice is bad for engineers the same way Wal-Mart driving other retailers out of town with low prices due to their size was bad for small businesses and small towns in the 90s and 00s.
You're acting like the employees were forced into the limos at gunpoint. People have free volition. Offering someone a better opportunity is not remotely 'evil'.
Dumping is basically not enforced, even if it is against the law.
Monopolies and cartels are against the law, but not enforced.
It is a sad reality of the modern economy, and one of the biggest indicators of who actually runs America.
At least in this case workers made money.
If borland was losing money, why didn't the execs negotiate a merger if they had so much desirable talent?
Hmmmmm, I bet the execs couldn't negotiate a big enough reward for themselves in an acquisition. The limo pickup at lunch strikes me as a big middle finger to Borland's management.
Of all of Borland's products that I liked, did I like them because of the software devs or the management? I guess what I want is the borland devs back.
If the fault lies on anyone, it's the employees who accepted the offers. If they really thought it was "evil", they would have denied the offer on moral grounds or in loyalty to their employer.
Do you not frequently get offers for more money than you are currently making at your employer? I would be a massive asshole if I accepted and left a job every time I got one of those -- especially in this market!
Since they succeeded in hiring so much of their company away, it seems none of them felt particularly attached to Borland or their work there, compared to a salary.
The only "evil" in the situation is how easily some (most?) people will abandon you the moment they get a better opportunity.
I suppose Borland could have matched salaries or tried to keep their employees in whatever way (maybe they did, who knows?) but at the end of the day either they didn't, or it wasn't enough for those engineers.
It's a dick move, and I wouldn't do it, but I am also not beholden to a board of investors/shareholders that expect to see positive ROE at the end of the day.
This is part of Microsoft's core culture. Bill Gates championed the philosophy of doing anything it takes to get ahead, as long as there's some argument that it might be legal.
So what I left out of my comment are the ethical implications of doing whatever you want, as long as there's no law against it. Many behaviors are unethical, while still (for the time being) legal.
Wait till you hear how they compete for suppliers, customers, and regulatory changes. Business is about gaining an advantage over a rival. Scoping up rival employees is a 2x activity, you get talent and a competitor has less.
Targeting all employees of a smaller company to destroy them is considered unfair business practice in some countries (legitimately IMHO). It's similar than selling at loss until your smaller competitor is out of business.
> It's similar than selling at loss until your smaller competitor is out of business.
Why is this considered illegal or unethical? This seems like a fairly legitimate tactical move to me.
It's like a war of attrition -- you allow yourself to suffer losses for the sake of ultimately winning. At least in this scenario, the main player is also slightly fucking themselves over, instead of just you.
It seems like there's a lot of this all the time though?
Everywhere I've lived, my only choice of ISP was Comcast. Whatever Comcast told me I needed to pay for internet, that's what I was going to pay lol.
For mobile phone providers, in the US your options are generally AT&T, Verizon, and T-Mobile, which I'm sure collude on prices and fix them. Same with Cloud services providers, etc
You can take a job and leave if they pay you more. That is fine. Microsoft isn't really only trying to gain talent. They want to drain the life blood out of their competition so they can get ahead. That intention is evil
It's a tactic. A dark one for sure. But corporations aren't known for being philanthropist anyway even if they spend millions on PR to mask that image.
As long as there's no enforcement (and in a free capitalist economy it's hard to enforce this, and I personally think it shouldn't be enforced too) these will happen. The best thing that smaller companies can do is to adapt and play by the rules if they can't change them.
No. One man's departure did not bring down Borland. Years after this guy left JBuilder was a great product that made them tons of money in the early 2000s. Java's popularity explosion (think J2EE) came years after the J++ debacle and JBuilder cashed in.
They disappeared because they weren't able to compete with the commoditization of Java IDE's (Eclipse) and Microsoft's integrated sales channel on Windows (Visual Studio). These two things killed their two biggest products.
Borland staff also disappeared because M$ made them offers that they couldn't refuse. Departing engineers were offered megabucks salaries which lasted only a year or two, but were enough to decimate the ranks of Borland's talent and wipe out the company's skillbase. Of course, Borland wasn't the only competitor to receive this kind of attention from M$.
In the 1999 federal prosecution of M$ for antitrust, Judge Thomas Penfield Jackson found that 'Microsoft used its "market power" to unlawfully "maintain its monopoly in the operating system market," violating the Sherman Antitrust Act. Microsoft, the Appeals Court found, unfairly used its monopoly power to strongarm computer manufacturers, Internet access providers, Internet content providers, independent software vendors, and companies like AOL, Apple, Intel, and Sun Microsystems.'
They weren't able to compete with those things in the early-2000's, yet JetBrains was founded in 2000 and has had nothing but growth and success ever since.
The quality of leadership at Borland fell off, and the organization lost its vision and ability to execute. Simple as that.
Maybe, but I really doubt it. "Our developers are cheaper" is rarely a winning strategy.
JetBrains did - and still does - execute well. They expanded their IDE to many languages and caught the Ruby, Node, and Typescript waves. Borland did JBuilder, yes, but it wasn't category-winning. Maybe Delphi could have dominated with more investment and more imagination, but it seems to have risen and fallen with Win32.
Their pricing strategy always sucked. I mean, 4000 Bucks for a Java IDE?
Jetbrains on the other hand did the right thing from the beginning by asking money but keeping the price realistic.
> They disappeared because they weren't able to compete with the commoditization of Java IDE's (Eclipse) and Microsoft's integrated sales channel on Windows (Visual Studio).
That, plus their weird and (IMO obviously even at the time) misguided pivot to emphasise SLM systems over dev tools. Well, it may be the same thing: seems likely this pivot was what led to them not being able to keep up with Microsoft on dev tools.
It's important to understand that in the 90s Microsoft was one of the few software companies that took "software talent" seriously, and would aggressively poach talent from competitors. They offered better pay, better working environments (private offices instead of cube farms). Often times their competitors wouldn't realize this until it was too late.
- DSL for UI (Forms)
- fast native compiler that produced self sufficient binaries
- great component library and many open source libraries
- Object Pascal was extended to fit perfectly the needs of UI programming
Building things that have no real-world constraints does often result in great beauty. Unfortunately, the web and all its ugliness became the dominant platform because it enabled no-download no-install information & application interaction
It was probably 20 or so years ago when I played for some time with Delphi. It was extraordinary easy to make program interfaces. Fast forward to today and we are in this clusterfuck, where everyone keeps reinventing the wheel and complexities just keep growing.
Yeah I feel that in a way, the best time to be a developer was back in the 1980s/90s. Your tools were limited but those constraints took away a lot of the "overhead" thinking about what frameworks to use and you could just focus on functionality. You didn't have Google or StackOverflow, but had a few books on your desk that covered pretty much everything you needed to know. Or if you were working on Unix, you had man pages, K&R, and Kernigan and Pike's The UNIX Programming Environment
Making resolution-agnostic applications in C# Winforms wasn't hard, it was a simple flag to tell the OS how to scale the GUI. And if you used the native widgets and set tab-indexes you'd be all set for changing sizes, blind users, OS re-theming, etc. A good UI framework should handle that stuff internally... even a bad one should do that (bad, like how winforms set the wrong default font).
Imho, the real reason we don't see stuff like this for the Web is that the web isn't designed for modularity. CSS, Javascript, and HTML IDs are all global.
Programming 101 lesson 1 is "don't use globals" and the Web is the perfect object-lesson in why not.
CSS - Yes. JS - Not since 2015, I'll admit that is somewhat recent. HTML IDs - IDs are only good if they're unique. Since HTML had no notion of scope, they became global. Shadow DOM is the web platform answer for modularization, however any JS framework will allow you to slice your CSS and HTML in components.
> if you used the native widgets and set tab-indexes you'd be all set for changing sizes, blind users, OS re-theming, etc
> Imho, the real reason we don't see stuff like this for the Web
Where are you looking on the web? tab-indexes and extending native web components gives you responsiveness and accessibility. The browsers provide theming capabilities for light and dark mode, and OS level color preferences (I use "red" for selected on Mac) easily show themselves on CSS `outline` etc
> Globals
No one uses globals on the web. This isn't 2000, or even 2013.
Everyone seemingly unaware that this still exists and you can still do it in Hejlsberg's C#? Drag and drop WPF components and program in code-behind? With themes and responsive design?
(Big asterisk: mostly Windows-only and has recently lost product direction coherency)
My biggest problem with the drag and drop builders was how it played with version control. The last I used was nearly 20 years ago - Windows Visual Studio C++ with MFC. Even if the builder produced C++ code, it was hard to know exactly where and how the changes were made. CVS (and maybe svn?) didn’t exactly like tracking those changes.
One thing I really liked about Delphi was its strict separation between generated and manually-written code. Delphi had a dedicated text file format that represented the form built in the GUI builder. So, VC would just pick up changes in the form file and save them like anything else.
Also Android Studio, XCode, all the React builder websites, etc. Basically every GUI platform + IDE has some form of a drag & drop interface builder.
The problem is that outside of the iOS ecosystem, there are too many subtle differences in behavior to really trust the results. And because a lot of software gets worldwide distribution these days, it's economically worth it to squeeze that last bit of performance & user friendliness out of the framework. So most professional programmers learn how to do things programmatically and only use the interface builder if they're doing a quick internal tool.
WinForms still exists and is fine for the odd quick utility. Doing WPF without ever having to drop in the XAML is... unlikely to say the least. You're going to end up in there are one point, because styles are fucking you over or for some other reason (databinding? lol). But yes, C# is still keeping the drag & drop alive. So are plenty of tools (Lazarus, hell even Android Studio has a drag & drop designer).
Delphi still exists and you can still do it in Delphi. Responsive. Cross-platform on Android, iOS, macOS, Windows, and Linux. Single codebase single UI.
Can you point to any Delphi app on the android playstore that doesn't look and feel like shit? Or a Linux app? I used to be a Delphi fan, but the results I've come across are not exactly convincing.
Compare this to Flutter, which looks and feels gorgeous, at least on Android.
I think forced aspect ratio was very common in the era of these oldschool UI toolkits. Additionally, handling multiple classes of pixel density and input (touch vs mouse) was unheard of.
> Fast forward to today and we are in this clusterfuck, where everyone keeps reinventing the wheel and complexities just keep growing
Yes, it is quite funny to see how no toolkit exists to simply produce Web UIs in a meaningful way.
However, the complexity has grown largely from externalities that didn't exist during the time of effortless interface builders, which is screen sizes and aspect ratios and pixel densities of all sorts. To handle this, you need to have some lower level primitives, and of course any time you have to go to a lower level you surface more complexity.
Final point - as a person who develops web UIs professionally for 7 years now, I think that the "reinventing the wheel" has been actually quite beneficial to tame this complexity. Previously, untyped JS had to be bent into surfacing type-style error messages, and good luck with boundary crossing data. Now, TypeScript lets you describe every key in your application and have incredible confidence that a fully-typed piece of UI or logic (which of course must avoid `any`) will deliver exactly what you intended. GraphQL & codegen has given us the ability to type our boundary crossing data straight from our DB or resolvers without any runtime reflection. Runtime reflection tools like io-ts also bridge that gap admirably to program defensively in the situations it's needed. It's obviously been accompanied by a lot of churn, but with strictly typed component libraries, a bit of reusable layout logic, and Hasura, I can make sexy fully-themable UIs strictly typed all the way to and from the data source without significant effort. The complexity in my new paradigm is entirely in application-level tricks like UIs visually informing users of all the async actions, animations / transitions, avoiding dynamic content causing bad layout blips, and ensuring user input is never lost. I think this kind of thing wouldn't have been easy in any oldschool toolkit because it inherently requires some wiring that isn't easy to surface
> where everyone keeps reinventing the wheel and complexities just keep growing
Cue XKCD "Standards" comic. People look at an existing framework and declare "this is total shit, I can build a better, easier to use version!" They then start building the better-easier and realize why the old version is so hard to use--because it's a difficult fucking problem begetting awful complexity + shitty code.
This repeats itself every 18-24 months, giving us the current clusterfuck of JavaScript libraries. Lather, rinse, repeat for the past 30 years (n.b. XWindows Athena -> Xt -> Motif/Lesstif -> ...<aeons pass>... -> Qt -> Electron)
But in today's reality, there is a lot of Javascript that is getting "downloaded and installed" into your browser's cache. It's all being managed for you and it mostly works.
Please, you must not be pedantic in this way, it's clear that I mean there's no install wizard and OS-native interactions the user must go thru, they just provide a string URL and immediately begin application-style interactions after a brief load
I mean, if not pedantic, then perhaps grinding an axe - he said 'there is a lot of Javascript that is getting "downloaded and installed"' as if that has anything to do with the user experience I was referring to
> any application (not just a browser) could provide the same download-interpreted-code-then-run-it functionality
I have never heard of such a platform besides the web. That is why the web became the dominant platform. I do not know what theoretical could've would've should've has to do with the reality of technological evolution
> It's probably not this particular feature of the web browser
... yes, it's not the ease of use that makes users like web, it's that computers in 2021 come with browsers installed that makes users prefer web over bloated desktop applications without good accessibility anyways!
I have no clue what your comment is meaning to get at.
>I have never heard of such a platform besides the web.
Steam comes to mind.
> ... yes, it's not the ease of use that makes users like web, it's that computers in 2021 come with browsers installed that makes users prefer web over bloated desktop applications
Wasn't comparing to "desktop applications." I was saying that the reason that the download-code-then-run-it functionality was shoved into the browser rather than coming in some other form, was that the browsers were already on all the desktops.
Compare and contrast today's Javascript-in-browser dependent applications versus a pure server-side-rendering model. With the latter, there is truly no software downloaded, only static assets such as images.
"In 1996, Hejlsberg left Borland and joined Microsoft. One of his first achievements was the J++ programming language and the Windows Foundation Classes; he also became a Microsoft Distinguished Engineer and Technical Fellow. Since 2000, he has been the lead architect of the team developing the C# language. In 2012 Hejlsberg announced a new Microsoft project, TypeScript, a superset of JavaScript."
I can only speculate that lots of skilled Borland developers followed Hejlsberg and participated in creation of C# and later TypeScript.