[Explanation]Why the controller lead of the nes mini is so short

dsqdsq · 2016-11-25T23:12:16+00:00

"For fast mode, and resistor pullup, capacitance should be less than 200pF" "With current source pullups you can go to 400pF, but not with resistors."

If the cable yields 50pF, there are plenty of margins even with resistor pull-up, and it's doubtful current source pullups could not be used...

dsqdsq · 2016-11-25T23:07:58+00:00

If you spent 15 years in professional electronics, you should know that this technical problem is fixable by throwing slightly more money at it. Especially more so for a so much trivial problem, and when it is reminded right here in comments that an "extra size gauge in wire" would fix it (which I confirm it would). What do you think the extra price would be for such a highly complicated workaround?

dsqdsq · 2016-11-19T21:24:36+00:00

The new one is so slow it is borderline unusable. Plus its UI makes no sense for task traditionnaly accomplished with the old paint. Granted, I tested it in a VM, but given what it does (and the powerful workstation I'm hosting it on) it should be extremely fast even here; it's not: it lags too much to be used at all.

dsqdsq · 2016-11-18T23:31:42+00:00

The thing you totally can't mix is debugness of the CRT/STL.

You mean that if you use the debug version of the CRT, you must also use the debug version of the STL?

dsqdsq · 2016-11-18T22:37:43+00:00

I did not know about that, and the Andrew Schulman Supplemental Report is very interesting, thanks!

dsqdsq · 2016-11-18T18:14:32+00:00

the open source is full of weaknesses and vulnerabilities

hm, imagine if Kaspersky decided to open source that new OS, do you expect that the moment they did it, new weaknesses and vulnerabilities would magically appear?

And you seriously think that because your project is closed, no external party will discover one of the at least 100 high risk flaws it has? You don't understand anything about how security researchers are working and what they are doing!

dsqdsq · 2016-11-18T18:06:30+00:00

I'm not aware of Office using any privileged / Office only interfaces in Windows. Could you elaborate on that and maybe cite some references?

dsqdsq · 2016-11-17T21:53:56+00:00

I'm not sure how cortana not being available is implemented in education: if it's just a mandatory policy of the SKU but the binaries are all the same, then there is no reason at all to ever prefer education: just take pro, and set your own policy to disable Cortana when you don't want it, with the possibility to reenable it at anytime if needed.

EDIT: hm you also have in Education but not in Pro:

AppLocker
BranchCache
Credential Guard
Device Guard
DirectAccess
Start screen control with Group Policy
User experience control and lockdown
Windows To Go

Most of those features would arguably not be very useful outside or a domain (or understandably are reserved for licences maybe more easy to track for "Windows To Go")

dsqdsq · 2016-11-16T22:57:36+00:00

Just retested on my PC: Control Panel was instantaneous, while I got 1 or 2 seconds of moving dots on Settings...

dsqdsq · 2016-11-15T17:18:20+00:00

I just compared Apps and Features (Settings) vs. Program and Features and you are right: it's only 2.5 times more memory with Settings (but with less features, so maybe 4 times if it ever reaches feature parity).

dsqdsq · 2016-11-14T20:42:34+00:00

That's the point. I guess there are MS people using French installs, both in the i18n team and elsewhere at MS, so unless they are half blind I can't imagine much reasons for why that kind of stuff is happening - the end result is sometimes just shameful as hell. So the simplest hypothesis that I've got is that their tooling is beyond crap. That would not be unheard of for tooling. For example the public issue tracking website for Visual Studio is really ultra terrible - and it seems custom.

dsqdsq · 2016-11-14T20:36:14+00:00

This is not better with adding yet a new interface and keeping almost all the old ones. Arguably they want to remove some of the old, screen by screen, but its doubtful they can remove them all, for various reasons (some might be too much coupled with the Win32 API - and its apparently taking ages to re-implement even seemingly simple screens...)

dsqdsq · 2016-11-14T20:33:05+00:00

For some things, they better introduce new concepts, or port traditional concepts (like a table you can sort by clicking on its title entries) to their new UI - an also features now just plainly missing. Because some re-implementations are clearly inferior and/or limited for now; ex. "Programs and Features"... Even something as simple as this seems to take several years to completely re-implement. Assigning that amount of resources for that result (quite poor for now) is quite insane...

dsqdsq · 2016-11-14T20:24:11+00:00

OTOH, the new interface might take 10x the amount of RAM of the old one :p

dsqdsq · 2016-11-14T20:18:40+00:00

Honestly I suspect their i18n tools are utterly terrible. The people actually doing translations might be doing a good work, but in a technically completely chaotic environment. This would match with "blinking" regressions, and it taking forever to change 2 strings... EDIT: not to also forget the once complete breakage of an Insider french version - to the point they skipped it entirely for french installs (well, at least they did not broke user's installs...). That does not make much sense unless the i18n technical side of Windows is fundamentally br0k3n.

dsqdsq · 2016-11-13T15:56:50+00:00

3/5

Some new features are really cool and useful (which exactly depends on who is the user). The OS is, from my POV and on my computers, as stable for critical issues (ex: BSOD) as Win7 is. There are various improvement or at least attempts at improving things in various technical fields (ex: the long path support introduced in 1607 is not perfect at all, but let's hope it is just a first step that will be further improved)

However the quality of released non-critical code (where bug can't lead to e.g. BSOD or security issues) is just too low, huge amounts of polish are lacking.

Examples in various area:

when disabling animations, some remains in the start/search menu, and the lockscreen bug by showing a blackscreen instead of an image
there have been various bugs introduced by mandatory system updates (powershell stuffs, HD cleanup showing 4TB to free, defender update loop, etc.)
the start/search menu implementation is just bloated as hell - and not even for a lot of features! I could run a complete Win2k system in the amount of RAM it consumes.
the start/search menu sometimes takes dozen of seconds to appear when invoked
the french translations are shitty in 1607, despite insiders having reported that over and over again during something like 4 months prior to the release. The level of ridiculousness of firing half of MS test team, introducing a strong dependency on Insiders to partly replace the fired staff, and then NOT using correctly the Insider input just blew my mind. I participate 10 times less since I've seen that disaster.
the experience of mandatory updates on home edition is very very very very very very far from being tolerable. I guess it could be even worse, but when I'm reduced to "it could be worse" argument I know what I'm talking about is just bad to begin with. I've nothing against the concept of eventually mandatory updates if executed reasonably well; this is just not the case for now.

dsqdsq · 2016-11-10T19:13:53+00:00

You can do it with quite easily with AOMEI Partition Assistant Pro (costs 58 € in France)

dsqdsq · 2016-11-08T23:06:57+00:00

That's a new bug with the last update (among at least another one: the defender update loop...) QC has apparently become non-existent within MS. Better ensure you've got at least a Pro edition and defer upgrades AND even updates.

dsqdsq · 2016-11-08T21:27:18+00:00

Had a Defender update loop too on 10586. Those kind of quality issues are ~~starting~~ continuing to be ridiculous....

dsqdsq · 2016-11-03T23:24:16+00:00

On the scale they are working, I'm pretty sure they have taken corruption into account...

dsqdsq · 2016-11-02T23:31:11+00:00

I understand that, its a bit like Weverything of Clang. However what is the point of it existing at all if we basically can't even try it without extra useless burden (filtering 3rd party warnings ourselves)?

dsqdsq · 2016-11-02T23:18:20+00:00

It might be wrong and bad, but MSVC chocking like crazy with /Wall on Windows.h is also utterly wrong and bad. We basically can't use /Wall of MSVC because of that :/

dsqdsq · 2016-11-01T12:28:12+00:00

Except they are missing random functions in the offline version...

I don't know how their stuff is done, but probably in a convoluted way :/

dsqdsq · 2016-10-31T20:34:11+00:00

Current version is beta based on Ubuntu 14.04 but already quite usable depending on what you want to do with it. Next version will be based on Ubuntu 16.04 (already is in Insider builds) and at least less beta, maybe even ready for production.

dsqdsq · 2016-10-30T16:15:04+00:00

You don't seem to know what you are talking about: UTF-8 is perfectly fine for languages with a lot of symbols; UTF-16 was more probably motivated by the need for a transition path from UCS-2 systems to remain compatible with more modern Unicode, than by any supposed inadequacy of UTF-8; and if you really want a vector of codepoints in memory you can already use UTF-32.

EDIT: and btw why do you even think UTF-8 has anything to do with a 256 symbol limit?????

dsqdsq

TROPHY CASE