Microsoft is a joke by itself

Dey broke our werkflow!

yes, and i hope that everyone who used that function did that. but its still hacky. why the extra step that wastes performance? (in case you have to read or write that value very often). ofc people argue "we hav da performunce!!" but that is the reason why my i5 struggles with some websites while games in my old vintage 10Mhz x86 run just fine.

Unfortunatly in this case not since the ShadowCopyFiles is a property and not a function. You could add a overload to the contructor of the class for it, but property names must be unique. Proprties behave almost exaclty like normal fields, because you access them identically; object.MyProperty = true; or return object.MyProperty;

It would be better to write a new function, and then change the implementation of the old function to just translate it's arguments and use the new one - that way you avoid the "deprecation lasagna" of a new function calling an older function [calling an older function, etc].

Our production code actually sends a fax to a team of interns. They have someone scoot over and flip the switch accordingly. It's more agile that way.

throw new NotImplementedException

Absolute genius. I still have a lot to learn!

If they are directly working with LED I guess it's probably in C?

What the fuck

The real wtf is always in the comments.

The reason for CTrue and True is likely because BASIC defines true as -1 while in C if you cast true to an int you get 1. So they defined both values here for both languages.

Mixed suggests the value was intended to indicate a range of booleans were not all one state or the other but had mixed states. Not sure what Toggle would be used for, except perhaps in a UI context to differentiate between checkbox (toggles) and radio buttons (not toggles). Weird though.

Embedded developer, passing strings around rather than enums? I can't see that going very well.

Oh no...

somewhat necropost, forgive me...

secure

free

open

source

licenses

?

Or am i missing something... (it happens)

This is not the way the world works for the most part, except for this new trend of subscription based services where you just "get" or are forced to take new things. It may be 2017 but people build businesses to stand the test of time without needing to commit a portion of their resources to solely maintaining items that are changing upstream when they themselves don't need new features. This is why part of Microsoft's empire is so large in the enterprise, because they have structured backwards compatibility in to their products to allow taking of things like security updates so you can benefit from them but without requiring code changes in XXX random application.

[deleted]

Keeping outdated software around makes more attacks like WannaCry possible.

But companies won't have better code just because you break compatibility. After a breaking change, they will just port their old code as fast as possible. If it builds, good, done, ship it.

The problem is that with the breaking change the assumptions the original coders had might no longer be correct. Just migrating from ASCII to UTF8 means opening a whole can of worms. Or the new API allows more or different access. Or the new API doesn't check for things the old did. Or vice versa.

Even just adding capabilities can be bad. Imagine an old file retrieval API that can only access local files. If a file is on a tape library, it just returns an error. If the new version can access those files, great, now your program hangs for fifteen minutes when such a file is requested.

I work at a company that thinks this way. We have a very large code base. I'd estimate at least half of all the effort I see going on is keeping up with people breaking shit out from under you. It's not a good thing.

Tell that to my company that refuses to switch from TFS to git.

python 3 is pretty good :d

also true, but there's no perfect way.

I still think it's bizarre that they keep Python 2 around, and that so many people continue to use it. They really should have just set a date and dropped it.

Wouldn't you release a version with deprecation warnings?

Node has got some positives going for it but it all just feels so...slapdash.

Well, for all it's great things, it's made by someone who felt that JS on the server was the best solution to a problem. Like.. They might be right, that's a different argument.. But you need to have a very special mind to even get to there.

Oh, I forgot about the obsolete attribute. That would make it a bit easier - but in that case you might as well just leave the old one there, marked obsolete (with warning, not error). That's enough to encourage use of the new without actually breaking the old.

It looks like it's returning a value from an environment variable or something. They could have interpreted it as a boolean, but if the variable is set to "banana" it's hard to make a unilateral decision about what that should mean.

Also, I've used libraries that required "true" or "false" instead of a boolean because they needed an "unset" value also.

Not from reddit.

The compiler compiles everything down to what's essentially a fake machine language that doesn't match any real computer. That fake machine language is fast to interpret, because all the operations are (usually) pretty simple. That fake machine language is often called "bytcode" because in the original languages that did this (Smalltalk, UCSD Pascal) back in the 80s, each machine code instruction was one byte long. The .NET programs call it ILM, Intermediate <mumble> CIL, Common Interpreted Language.

Since it's fake, you can compile your program once and run it anywhere there's an interpreter for that fake code. Java's version, for example, compiles into ".class" files, and uses the JVM "Java Virtual Machine" to interpret it. That's how you get Java that can "run on any machine." The JVM gets ported to a new computer, and then all existing Java programs can work on that new computer (in theory).

Nowadays, the fake machine code gets interpreted, but if the interpreter sees the same routine getting called more than a handful of times, it will "just in time" translate it directly into the machine code of the computer it happens to be running on, as it's running. So after that, it runs full speed.

.NET goes one step farther. When you install a compiled .NET program, there's a background task that eventually compiles the whole thing and stores the machine code back onto the disk, so once that finishes, you don't have to take the time to JIT any more. That's one reason why after some Windows Updates, you might notice your disk flicking around for a while.

Just In Time compilation. .NET assemblies are usually(?) not raw machine code but actually in an intermediate form, kinda like Java's .class bytecode representation.

I don't like /r/prequelmemes. They're coarse and rough and irritating and they get everywhere.

/r/PrequelMemes is a goddamned sieve.

It's more like a torrential downpour/flood at this point

blender.. a nightmare of key combinations... sucks when you only occasionally work with it and cant remember shit from last time and have to look up every single thing you want to do "how do i set the rotation to exactly 90°??? ohhh select the object, press n and a window comes up..."

well i might argue about the "great language" part, but yeah community is good and there are tons of libs/modules, but docs are lacking basic things like talking about special cases or exceptions

i usually work with c#, and the doc usually mentions what happens when for example a file is missing, or there is no permission. java (not that i like it) even forces exception documentation in its syntax. so the signature contains at least a mention of all the possible exceptions that can be thrown (id love to see such a feature as optional in c#, so there is an easy way to document exceptions in code, but you dont have to document every argumentexception ever)

Not a language per se, but if you're used to man files on a Unix/Linux platform the Python documentation does feel... deficient.

Ironically, Java is pretty thorough just due to age. You have to read the source more often than I'd like, but it sometimes actually warns for unexpected pitfalls, and it hardly ever lies the way Microsoft and Android docs do.

yup, which is why i usually use statically and strongly typed languages where i dont have to deal with the bogus that dynamic and weak typing brings with itself. so many hours wasted, which could be saved by just checking for such things at compile time

but maaayyyybe i dont have time to search through the source all the time when i want to know what exceptions are thrown? i need to get the product going, and searching code for answers that should be in the documentation is quite annoying

Bruh Python be chill yo i mean i roll that from time to time and shit but it's just a language and shitty, hard to process code is written in it all the time just like any other language furreal tho

Python done right, as in proper PEP8, sure. I've seen a lot of shoddily written Python code that would be a whole lot more useful to expand upon, with documentation.

144p and patience.

After a week of data collection, the numbers came back… and they were baffling. The average aggregate page latency under Feather had actually INCREASED. I had decreased the total page weight and number of requests to a tenth of what they were previously and somehow the numbers were showing that it was taking LONGER for videos to load on Feather.

just wait .....

Very patiently.

And there's lots of "videos" where people share music albums with a static image as video feed. Those have fairly small overhead over pure music streams… if you can load the page in the first place.

function IsOn()
    var RetVal;
    if( IsOn == true)
    {
        RetVal = true;
    }
    else
    {
        RetVal = false;
    }
    return !RetVal;
}

So

!isOn

Too easy :/

Haskell, F#...

BASIC

ES6 Javascript.

Rust

JavaScript 2015 or ES6 (same thing).

Haskell, F#

Visual Basic

English uses it, fairly certain.

This represents a database table, so it represents column named type. They simply didn't want to name the column "quality_control_type" to not cause confusion with the QualityControlType model bellow.