In any case, this was posted along the discussion here, and you might find it interesting: https://www.gnu.org/licenses/translations.en.html
261 karma · joined June 7, 2018
In any case, this was posted along the discussion here, and you might find it interesting: https://www.gnu.org/licenses/translations.en.html
Their signature was not required for the constitution to enter in effect. It was desired (it still is) but since the refusal was (and still is) mostly political, it is not regarded as a major impediment.
Keep in mind two-thirds is a qualified majority.
RMS may not be a fool but he is still American (and not a lawyer). I don't think he was focused in solving licensing/copyright issues in the rest of the world in the early 90s - and even late efforts for GPLv3 didn't change it that much.
https://gist.github.com/matey-jack/3e19b6370c6f7036a9119b79a...
In fact, the Rust book explicitly mentions doubly linked lists when discussing Pin:
https://doc.rust-lang.org/std/pin/index.html#example-intrusi...
The ownership system might make it less trivial to implement, but the statement that you cannot implement it in safe Rust is incorrect regardless.
But you don't have to go to that extreme. For instance, I just heard today of a lost contract from a coworker: the client was fed up with a call management system that was dropping calls like crazy and nobody was able to fix since you could not even replicate the system (the last time they tried it, the test system pulled stuff from the production db and it basically brought everything down).
How do you calculate the cost of this? Cost of debugging, lost revenue, lost referrals, brand damage, and the toll on developers and everyone doing crisis management.. I'd say 100x is a very optimistic estimate. It can very well cost much more than that.
Trivial bugs are trivial bugs, and not all the bugs are the same. A misaligned table is nothing compared to a monolith/blob of 50Mb (either a binary compiled from C or minified JavaScript) that crashes with "segfault" or "undefined" but runs fine in debug mode.
Bottom line: bugs in production, especially on complex systems, can be very hard to identify and fix - and sometimes can cost you your business.
"Researchers have mostly studied the effects of cannabis and nicotine on people with schizophrenia. But they’ve also found that other things that alter your nervous system and mood (called psychoactive substances), like alcohol, can trigger first-time psychosis."
Source: https://www.webmd.com/schizophrenia/features/alcohol-schizop...
IOW, if you have predisposition to schizophrenia (family history, previous psychotic episodes), you should avoid mind-altering substances.
Edit: word
Tokio benchmarked io-uring vs epoll with synchronous I/O, so "up to 60%" is within the expectations.
I suppose not, if you are considering "we" as "the set of people that designed languages like Go or justify the design decisions made by such group".
If you are considering "we" as humanity, in general, I'd say that no, "we" actually learned a lot and "we" already know better. But you still have some building rockets to try to prove the earth is flat, unfortunately.
I don't know why you keep bringing this algorithm to the discussion, everything that was mentioned applies to any linked list. It's a fundamental property of linked lists, period.
Seems like you're completely missing the point: the discussion started on performance properties of data structures. That's what's being pointed out, and it's going to be a fact regardless of how you want to apply it.
Lists will eventually become a problem since your next/prev pointers may not be pointing to adjacent memory positions, now your linear iteration over elements will not be cache friendly. Not only that but you need to retrieve pointers and dereference them, more pressure and worse for the cache again. You also add a "load" dependency between all elements so you can't easily break processing between multiple cores.
Lists may be conceptually elegant but they are not the most suited for performance or efficiency.
IOW: typed languages are better, period.
Even if you had to use notepad to program - or had very basic syntax highlighting - wouldn't be what the language provides a more compelling point to make these choices?
To be honest, it's hard to disagree with him on this, even being in favour of welfare and/or socialized healthcare systems.
"The H 1B also requires that the H-1B employer pay the H-1B employee the prevailing wage or the actual wage, whichever is higher. The prevailing wage is the salary paid to workers in similar occupations in the geographic area of the intended employment. The actual wage is the wage that the employer pays employees in similar occupations at the location of the intended employment.. Since the procedures and record keeping required for the H-1B are complex, an attorney or other trained person will be necessary to complete the paperwork."
Apple has a strong name in North America, but I find that to be mostly based on a perceived image, rooted more in a distant past (or on pure marketing) than in reality. I understand when this happens with the general public but it puzzles me when technical people buy into this.
If you need anything more advanced you should do an assignment to allow time for proper design and reasoning, otherwise you'll never be able to fully evaluate what the candidate really can do and how he/she approaches problems.
AFAIK, this is all part of the roadmap.
[1] https://www.janestreet.com/tech-talks/effective-programming/
This all applies regardless of the C++ standard, of course.
"Metaprogramming is a programming technique in which computer programs have the ability to treat other programs as their data." [1]
i.e.: it's a programming technique and not something related to any process related to building code.
I understand the idea of giving some more practical side of using computers in a "missing semester", but please pay attention to the nomenclature. It can be really confusing for someone studying CS that does not yet grasp the concepts that well.
This is a problem I have with Python: everything is assumed to be a standard GNU/Linux/desktop environment, you are assumed to always have to have the latest versions of everything (or to have "up to" a certain version, which then breaks everything else that relies on the latest), and all becomes sub-optimal if you deviate a bit from the expectations.
Now this is fine for some people but you can't blame the ones that have different environments. This is why most people doing actual embedded cringe when someone suggests using Python, because the experience is not usually pleasant.
I spent some time working on a RN project, and even though the whole idea of declarative interface, state update, etc is interesting, it is not exclusive of RN - and there is the whole rest of the story: RN libraries are a mess and usually buggy, there is virtually very little compatibility between native and web, and.. have anyone ever tried updating a RN codebase?
I remember we had to recreate the full project and copy the files manually because everything was broken beyond any hope, this after spending a full week trying to fix the build.
For Shopify seem that even a PWA could fit, and would be much more compatible, reliable, etc.
By the way, one of their justification is "in-house know-how", which I heard so many times before... This is usually how you justify crappy decisions by using inferior technology and then spending 2x the effort to try to fix it. I hope it doesn't happen with them, but it does like like that's the way they are heading to.
A coworker tried using an availability light but.. good luck trying to get people to respect it. Either people will miss it, forget it, or ignore it (specially if they are above you on the org chart).
I tried mufflers a few times, but it didn't work that well. Same issue as availability light, plus the fact that everyone looks weirdly at you and initiate conversations when you have the mufflers on..
So what I did was push working from home more and more until I went to working 1-2 days from the office per week. Now I have a much better productivity, ability to focus throughout the day, etc, besides all the advantages of not having to commute 5 days per week.
We cannot know if milk (in general or 1%) is causing aging or protecting against it, cases which point for very different conclusions.
This table also has something interesting that corroborates with this idea:
https://new.hindawi.com/journals/omcl/2019/1574021/tab4/
Note how the ones that rarely drink any milk have the same telomere lengths, same as the ones that drink full fat or 2% milk. SE is also so big for 1% and non-fat on the "rarely" row that telomere lengths can be considered to be the same for all the columns (on this row).
It makes me wonder if it's the milk or if there is any other covariable that is playing a role here. In fact, they themselves cite this in the study ("Discussion" section):
"However, it is possible that other dietary differences account for some of the biological aging differences among the milk fat categories."
Therefore, I'd take this study with a grain of salt. If anything can be concluded by these numbers is that 1% milk may be protective, not that full-fat milk promotes aging.