41–48 of 48 posts
Earlier quoted context omitted.
And they've open sourced a lot more than just .NET Core. https://github.com/Microsoft/dotnet
http://microsoft.github.io is a metasite with links to most of the Microsoft GitHub organizations and repositories. You can spend days flipping through all of it.
Earlier quoted context omitted.
The jTDS project is dying, there has not been a new release in over 3 years despite some pretty significant bugs. https://sourceforge.net/p/jtds/discussion/129584/thread/050f...
Yeah, maybe we'll switch as well now. But I just cant stand the loving hype for MS here. They gave out such horrible and dog slow drivers to their paying customers that people reverse engineered the protocol and wrote their own. And it still performs very well. Now that MS publishes this codebase (which should have been standard, or at least best, practice), they get showered with love. Like an abusive relationship w…
Earlier quoted context omitted.
http://microsoft.github.io is a metasite with links to most of the Microsoft GitHub organizations and repositories. You can spend days flipping through all of it.
the carousel on top has four pips but three items. my ocd is at critical levels right now. (possibly something got filtered since i'm at work)
Earlier quoted context omitted.
Yeah, maybe we'll switch as well now. But I just cant stand the loving hype for MS here. They gave out such horrible and dog slow drivers to their paying customers that people reverse engineered the protocol and wrote their own. And it still performs very well. Now that MS publishes this codebase (which should have been standard, or at least best, practice), they get showered with love. Like an abusive relationship w…
You don't need to reverse engineer the protocol. TDS is an open spec on their website.
How did people use this before if it wasn't in the Maven Central Repo? I know it's possible to not use mvn, just wondering what people did in cases like this where a possibly major component in the stack was unavailable. Most big stuff in Java can be found in mvn, and if not we often end up using an alternative. But that's not so easy for a driver.
The driver is only needed at run time, not compile time, at least in this case.
Earlier quoted context omitted.
The jTDS project is dying, there has not been a new release in over 3 years despite some pretty significant bugs. https://sourceforge.net/p/jtds/discussion/129584/thread/050f...
Yeah, maybe we'll switch as well now. But I just cant stand the loving hype for MS here. They gave out such horrible and dog slow drivers to their paying customers that people reverse engineered the protocol and wrote their own. And it still performs very well. Now that MS publishes this codebase (which should have been standard, or at least best, practice), they get showered with love. Like an abusive relationship w…
While Microsoft claims the new driver is fully JDBC 4.1 compliant key JDBC 4.1 methods throw SQLFeatureNotSupportedException and the code is littered with comments
// The driver currently does not implement JDDBC 4.1 APIs
Nice. Microsoft seems to be open-sourcing a fair bit of stuff lately. However, unlike their other repos there are a couple of things that strike out. The code isn't even consistently formatted. There are parts that make you say ouch.
Earlier quoted context omitted.
Microsoft is a tech company just like many others. You can nitpick all you want but all companies have imperfect code and it is normal.
Sure. I don't fault them. Just curious that Microsoft doesn't force a linter on devs. At google we generally force style guide compliance.