I hope that with them gone the project doesn't revert to the mindset of "everyone gets their own fiefdom (workbench) to manage" that's resulted in instabilities and fractured user experience in the past.
599 karma · joined December 7, 2016
I hope that with them gone the project doesn't revert to the mindset of "everyone gets their own fiefdom (workbench) to manage" that's resulted in instabilities and fractured user experience in the past.
Not trying to disrespect the other FreeCAD developers, but it seems like things have improved remarkably since ondsel started taking a more active role.
The project seemed to exhibit a (common) impulse to prioritize extensibility too much. The "workbench" architecture and python API let you do some really neat stuff if you're willing to dig into the weeds. But, from the perspective of a community outsider (so take it with a grain of salt), the development process seemed to be a good example of Conway's Law in action. The workbenches let everyone have their own sub-projects to manage without stepping on each other's toes. This led to a lot of resulting complexities, inconsistencies, and instabilities, which made the approach a net negative (imo) in terms of tradeoffs.
With ondsel, there's been more focus on holistic improvements and getting the individual modules working together more smoothly, which I greatly appreciate.
If not, you might run into [this bug](https://old.reddit.com/r/linux4noobs/comments/uj58i5/psa_fix...)
FWIW my solution was using equivs to create a dummy package to satisfy www-browser and installing that.
I've also been running into an annoying issue where hover menus will randomly stop working---it seems like the mouseout event is firing before the click event is handled.
But all in all not annoying enough to switch.
void log(Supplier<? extends String> messageSupplier);
log(() -> log.info"User is \{someExpensiveFunction(user)}");
The pattern of using Supplier to provide a lazy argument is pretty well-established afaict.The only way to have the option to have your preferences met in a large and mature enough market is to be completely price insensitive.
Of course, this is a loophole big enough to sail a cruise ship through. And the Senate takes full advantage of that loophole in practice.
Another possibility is writing a native app that works like a shim: reading from the COM port and using APIs (e.g. SendKeys on Windows) to re-transmit the characters as keystrokes. But the most robust solution is probably a different scanner.
The complaints in the original article fell rather flat to me, but this is one area where it's absolutely fair to criticize VS. More generally, the reason that build tooling in the .net sphere is such a mess is because of historical baggage from VS.
With that said, if you're coloring within the lines[1], VS is very powerful and productive.
[1] To an extent. There definitely are use cases that are "supported" only in name.
They've already started down that road with s mode, which is default for new installs and not a separate SKU (anymore) that you can avoid.
Microsoft in general has a tendency to bolt on functionality in a kinda slapdash manner when another team wants it, so you get a lot of cruft that really doesn't belong in the Task class[1] but is there because someone wanted a way to handle their special case so it just got thrown into Task.
[1] See https://source.dot.net/#System.Private.CoreLib/Task.cs,045a7...
The problem is that Task/Task<T> was the foundation for async, and it's a bad foundation. Even with the ability to write your own duck-typed awaiters (and the advent of ValueTask), the widespread use of Task means if you're writing async code you're going to have a tough time getting away from it.
WRT why I think strong encapsulation is a bad goal: I've worked extensively in .net where assembly-private members are the norm for core libraries. It has issues. Classes and methods that are theoretically extensible aren't so in practice because core logic is inaccessible.
In the end, encapsulation, no matter how strong, doesn't prevent people from relying on internal implementation details. If the concern is people relying on "internal" APIs, either suck it up and make those APIs public (with all that entails) or come up with a deprecation strategy (or just freeze them and refactor around them).
> It is alleged that WikiLeaks solicited material by publishing a list of information it wished to obtain, its “Most Wanted Leaks”. In November 2009 this list included: “Bulk Databases” including “Intellipedia”, (a non-public CIA database) and classified “Military and Intelligence” documents. In December 2009, Mr. Assange and a WikiLeaks affilia te gave a presentation to the 26th Chaos Communication Congress in which WikiLea ks described itself as “the leading disclosure portal for classified, restricted or legally threatened publications.” In 2009 Mr. Assange spoke at the “Hack in the Box Security Conference” in Malaysia in which he made reference to a “capture the flag” hacking contest and noted that WikiLeaks had its own list of flags that it wanted captured.
> Between November 2009 and May 2010, Ms. Manning was in direct contact with Mr. Assange using a chatlog (the “Jabber communications”). On 8 March 2010, it is alleged that Mr. Assange agreed to assist Ms. Manning in cracking a password hash stored on a DoD computer. Mr. Assange indicated that he was "good" at "hash-cracking" and that he had rainbow tools (a tool used to crack Microsoft password hashes). Ms. Manning provided him with an alphanumeric string. This was identical to an encrypted password hash stored on the Systems Account Manager (SAMS) registry file of a SIPRNet computer, used by Ms. Manning, and associated with an account that was not assigned to any specific user. Mr. Assange later told her that he had no luck yet and asked for more “hints.” It is alleged that, had they succeeded in cracking the encrypted password hash, Ms. Manning might have been able to log on to computers connected to the classified SIPRNet network under a username that did not belong to her, making it more difficult for investigators to identify her as the source of the disclosures. It is specifically alleged that Mr.Assange entered into this agreement to assist Ms Manning’s ongoing efforts to steal classified material.
> On 31 December 2011, WikiLeaks tweeted “#antisec owning Law enforcement in 2012.” It included links to emails and databases confirming that Hammond and AntiSec had hacked two US state police associations. On 3 January 2012, WikiLeaks tweeted a link to information which LulzSec/AntiSec had hacked and published in 2011 headed,“Anonymous/Antisec/Luzsec releases in 2011.” In January 2012, Hammond told Sabu that “JA” had provided Hammond with a script to search the emails stolen from Intelligence Consulting Company, and that “JA” would provide the script to associates of Hammond as well. Hammond also introduced Sabu via Jabber to “JA.” In January and February 2012, Sabu used the chatlog Jabber to communicate with Mr.Assange. On 27 February 2012, WikiLeaks began publishing emails that Hammond and others hacked from the Intelligence Consulting Company. On 27 February 2012 Hammond told Sabu, “we started giving JA” materials that had been obtained from other hacks. On 28 February 2012 Hammond complained to Sabu that the incompetence of his fellow hackers was causing him to fail to meet estimates he had given to Mr. Assange about the amount of hacked information he expected to provide to WikiLeaks, stating, “can’t sit on all these targets dicking around when the booty is sitting there ... especially when we are asked to make it happen with WL. We repeated a 2TB number to JA. Now turns out it’s like maybe 100GB. Would have been 40-50GB if I didn’t go and get all the mail from [foreign cybersecurity company].” Hammond then asked for help with ongoing computer intrusion committe d by his associates against victims including a US law enforcement entity, a US political organisation, and a US cybersecurity company. In March 2012, Hammond was arrested.
> In June 2013, media outlets reported that Edward J. Snowden had leaked numerous documents taken from the National Security Agency and was in Hong Kong. It is alleged that, to encourage leakers and hackers to provide stolen materials to WikiLeaks, Mr.Assange and others at WikiLeaks openly displayed their attempts to assist Snowden to evade arrest.
[1] https://www.judiciary.uk/wp-content/uploads/2021/01/USA-v-As...