skysight-inc/HackerNews huggingface dataset:
"Copyright is useful, just not in its current state where it's being abused."

I'd agree—and I'm not contradicting my earlier comment by saying that. It's that what passes as breach of copyright and patent law is so finely ground that neither corporate or national interests are properly served.

So much time is wasted on protecting stuff that either isn't really a breach (so close to prior art) or on developments that are so trivial that they effectively amount to very little, that is the overall net result/outcomre is negative (even the winners only achieve a Pyrrhic victory).

The only people who truly benefit from this over-grinding of the law are those in countries whose laws allow more flexibility. The over-fine grinding of law also acts as a disincentive as it's intimidatory, people aren't going to invest in developing products if they have to spend most of the profits from them on litigation brought on by competitors whose principal aim is to just thwart competition.
Market research or product fit
Well shouldn't be too difficult to test these hypotheses, if the AI approach is better then actually run a study and show that!
So we should all start smoking to look cool and attract other cool smoking friends
Corporation will almost never give you a raise if you don't ask. In their interest is to pay as little as possible and they also need to be careful - if they pay too much, you may amass capital and leave to start your own business.
So these things need to be balanced.

You have to be prepared to quit. Here in the UK the most effective way to get a raise is to actually find a new employer and ask 15-25% more than at one's current place.
I don’t know — do you have to know how an engine works to drive a car? While they may not understand at first why they have to write this, I really dislike when people make that 3 words into something impossible to grasp. A good chunk of all programmers have learnt to program by starting with Java. And besides these 3 words, it is a small language (very few keywords), easy, but sufficiently strong type system that will catch most of your problems at compile time, and first and foremost, very well-defined runtime semantics, even when errors happen, all of which help beginners greatly.
Yeah exactly, it makes everything so much more ergonomic, especially with combinators, as in chaining method calls that might return an error
> it will only require an additional 17% to the current electric generation.

That.... That is not an "only". Switzerland's total consumption is 58.46 billion kWh [1]. "Only" 17% increase is another 9 billion kWh. That's the equivalent of Estonia

[1] https://www.worlddata.info/europe/switzerland/energy-consump...
> There’s no good excuse for the lack of women bricklayers, plumbers, mechanics, and loggers, but no one’s worried about that.

Yes, actually, people are worried about that even if people whose attention is more focused on tech may not see it as much:

https://www.constructionnews.co.uk/agenda/inspire-me/percent...

https://www.theguardian.com/careers/careers-blog/2015/may/19...

Etc.
A lot of phones do, eg most Samsungs since the S20 have physical and eSIM.

There's also an interesting product from https://esim.me/ that emulates the functionality of an esim on a physical sim card, and lets you switch between eSIMS via their app even on older phones like the galaxy S8.
I disagree. The big point of the determinism is that you can actually trivially control when deallocation occurs. In fact even if you don't want to manually reason about there are tools which can graphically show you when objects are deallocated.
This sounds feasible at all for you for all the millions libraries in npm not to be labelled as "obsolete"?

Yes. I mean, they could just leave the max version of the engines property blank because it should always work if it's something as trivial as leftpad, but in a well-run package repository the work of checking library compatibility should be getting done. The fact that NPM is full of old libraries that haven't been tested in new versions of Node is a bad thing, and those libraries should be flagged as untested.
Twitch lost the battle for its soul
You should have a customer ready to pay you before you write a line of code. Preferably multiple customers. If you can sell to your target market without a product you can sell to them with one!
How about not choosing a project name in relation to a well-established city in egypt? /s

Like the space for project names is pretty much overloaded multiple times already. Unless we start to use funny words of the dictionary like 'carbuncle'.
I think the common usage for the original begging the question would probably be tautological reasoning nowadays.
My grandmother was born in 1895 and died 1987, she went through all you listed and something you forgot (and many more missing):

- photography (in the family, outside professional shops)

- electricity in homes

- radio

- television

- spanish flu (she lost her first born in 1918)

and she was just fine, as a matter of fact she remained curious about everything ( and this probably helped her live for such a long time with a perfectly working brain till the very end).

My mom is now in the same ballpark (born 1930) and she often brings up this topic, all in all she believes that she witnessed much less changes than her mother, most of what she went through were refinements and betterings of existing technologies rather than "revolutionary", as an example the telex and fax were essentially evolutions of the telegraph, what she points out are:

- electric dishwashers and washing machines

- computers/internet

- cellular phones

I don't think that if we live to that age we will see many "new" things.
Whilst your point is fair, I do think the fitt's law benefits are pretty huge (ie the infinitely extending target because it's across the screen edge).

It really depends on usage patterns I guess. If you have lots of _really_ small windows then your point is entirely correct, but if people are using large windows then it becomes less clear - there's a fair chance they're moving almost as far to reach the edge of the window for the in-window menu bar, but not benefiting from the screen edge infinite target, at which point the macos model becomes superior.

The thing is I suspect the cut-off applies even for half-screen windows these days, I think the benefits of screen edge scale better than the benefits of window edge (since you can always move faster if you don't have to aim well). On the other hand, I guess there's an upper limit to practical window size, regardless of how large screens get.
A lot of asian countries have similar convenience for physical SIMs, order online and just pickup at a stall at the airport.
The Missing Locksmith
And presumably little old Steinway struggles on in Queens?
This argument is often used as an excuse. What "personal data"? I just want to browse and find the products available at local Target stores. Or buy coffee with a gift card.
> I am deeply hurt and disappointed with way corporate works. I feel cheated.

I feel this every day and I’ve been working for over a decade. Work has so little to do with getting things done and being rewarded.

Ask your manager who to talk to about getting a pay rise. Hopefully it won’t be your direct manager because they might get paid less than what you’re asking for. Come prepared with a list of responsibilities that are above your current pay grade. Don’t bring up fairness. Ask for a rise a few k above what you think you can actually get. Ask your coworkers their salary if you’re brave. Be aware that management will probably fob you off and tell you the pay rise is impossible and you don’t deserve it, you’ll come away feeling devalued and stupid, but they’ll probably grant it anyway. Don’t expect regular pay reviews to come to you (my managers have looked flabbergasted when I said it should be the main point of the appraisal/review process), make sure you’re bringing up pay regularly yourself.

e: also, once you get the raise, slack off a bit. It’s not like they can reduce your pay.
Indeed, although I use macs daily for over a decade now, the whole "consistent" placement of the app menu at the top of the screen has struck me as idiotic from day 1. On a 27 inch iMac it was already a nuisance, on a 43 inch wide monitor it is downright silly. My preference would be to make it a setting, as I can see there are cases where it does make sense, e.g. multi windowed application with palette windows and such, if one so prefers.
i have. they're treated well. and no, never in my uni years I heard any creepy behaviours done in our department by our students. oh, and it should be noted that half of our students are women (iirc almost all of them graduated in time).
I'm not from the US either, but I don't think that asserting that all people should be treated equally is "politics". Actually it's a basic human right that I think most of us agree with - at least in theory, the problems only come when applying it in practice...
Yes, that's basically the whole point of the article - an assumption they may not have made all too consciously to use RDS turned into a bad decision they sought to rectify.
Eh...

This is how marketplace companies work. Provide unsustainable incentives to attract creators and consumers. At a certain size, you must raise prices in order to make a profit.

I don't see a problem with what Twitch is doing.
Quite nostalgia-inducing with the ugly gradients
>is subjective, not factual.

That's fine, it still doesn't mean "anything goes". Not all subjective things are "just personal taste".
Are you saying that he has a rubber mask on his face? Because the face is what I'm talking about. The eyes shape, the cheekbones, the nose. Even the hand plays into this hypothesis. I don't need a costume to deduce that someone looks Mongol.

However, speaking of costumes: while ‘a wrinkled old hag as a villain witch’ says Baba Yaga, the long hat is not a feature of cultures in and around Russia, or in Asia in general to my knowledge. Neither old hags nor witches need such hats here.
These issues were also brought up immediately when the language was first shown, alongside nulls, tuples, error handling, etc…
You've been doing it wrong: I practice shrinkflation principles, and work one less minute every month. That way, I effectively get a 2% raise at the end of every year.

If the company isn't satisfied with my performance, they can give me a raise to work more again.
This is a great read! Mark Cranney the author is the sales leader Ben Horowitz talks about in his book "The hard thing about hard things". He was known even at the time for being very aggressive sales leader
> I work extra hard and spend overtime to run this team.

This is a big no! Please don't do that. You are not a charity and this is not your company.

If you want to continue to do that, at very least write down the extra hours you work so that you can calculate your real wage and maybe if you see how much less you actually earn when you do that, then it may compel you to stop.

When my friend accounted for all the "all-nighters" and evenings, she realised that she was actually paid slightly over the minimum wage. It's wrong.
some googling led me to this: https://www.youtube.com/watch?v=fEAztJdKN88
not sure if it's the one mentioned by GP. the channel that posted this video seems to have others on the subject.
That's for single head, yes. From my point of view, single head is the norm here. In here too, I would imagine multi-head to be cheaper per head than single head.
Awesome channel, puts out consistently high quality content and I find the narrator to be better than a vast majority of similar channels who seem to all have the same annoying voice quirks which I think they do intentionally.
Apple makes iPhone 14 in India in shift from China
NVME? You can serve this from a raspberry pi.
Only if you configure them to do so. I created our Globalprotect solution and we use docker extensively without issues. It just sets a default route (0/1 and 128/1) and users just need to NAT from the docker network for it to work.
> What happens if the project is abandoned after you chose to rely on it?

If the project already had the features you need, was thoroughly tested and debugged, and was built with almost no dependencies (only relying on a small number of very stable platform APIs), then it might not matter even if it was already abandoned when you started using it.

Case in point: On a recent software project, I took dependencies on two Lua libraries which were already abandoned. Their source code was short and readable enough that I had no problem going through it to understand how they worked. In one case, I added an important feature (support for a different type of PostgreSQL authentication to a Postgres client library). I also packaged both libraries for my Linux distro of choice and submitted them to the official package repositories. If anyone reports bugs against the version which I packaged, I'll fix them, but it seems unlikely that many bugs will ever be found.

As the OP rightly pointed out, the expectation that software libraries should normally need to be constantly updated is ridiculous. Many other things invented by humans stay in use for decades with no alterations. Beethoven's 5th symphony hasn't had any updates in more than 200 years.
I think both langs have their strengths, neither is clearly superior. If F# added a few more language features though...
Stupid question, the unit scripting language used is javascript?
So in theory, all units script execution can be outsourced to a part of the gpu?
https://gpu.rocks/#/

Sorry, this is barely gameplay related, just interested if that could be kept synced.
I honestly wonder if it wasn’t also influenced at least a tiny bit by people wanting a decent purple named colour. I know it had always grated with me that pretty much all the other colours were fairly well-represented, but there just wasn’t a good purple, and I regularly use rebeccapurple as a temporary colour, because of its value, not its history.

(I’m not suggesting this was a conscious factor in any way, but at the same time it wouldn’t surprise me if in an alternate history where Becca’s favourite colour was green or blue that the entire thing wouldn’t have come to fruition.)
While that may look good for a hypothetical example, I'm not sure how beneficial it is in real-world use. If your higher level functions are directly passing errors from your lower level functions then you start to bake implementation details into your abstractions which becomes a nightmare later when your implementation changes and callers are depending on those details. In reality, you need to deal with the error immediately and, if there is no better option, return your own error that describes the problem in a non-implementation-specific way.

It is possible that with other error-related features added to the language you could avoid those traps, but Go doesn't feature those either, so simply adding that construct without thinking about the problem much more deeply doesn't buy you much.

If you are solving a stop the world when you encounter an error-type problem that might be okay, although I'd argue that you may as well panic instead. But, again, Go isn't designed for those problems and I'm not sure it needs to be. There are already plenty of good languages designed for that type of work.
Can you transfer the eSIM if the source device is broken?
Oddly enough I hear these recommendations here in Ireland as well, even though we're generally a culture that hates bragging in all its forms. Maybe this is rooted in the English-speaking world in general?

The main argument I hear is that phrasing achievements in a team centric way makes it sound more like you're claiming the achievements of others. Eg:

- I developed project X increasing revenue by Y

- Part of team A which developed X increasing revenue by Y

Depending on how you phrase it the individual statement could sound like you're unrealistically claiming what must be group achievements, or the humble answer could sound like you had nothing to do with the achievements at all and are trying to claim some bare meaningless connection to success.
Of course this will be blamed on Russia.... All the BBC's and CNN's will quickly catch-up on this and launch a coordinated attack on Russia now.
In a software development context, the functionality should be specified by analysts, not by the manager. The technical architecture should be specified by an architect, not by a manager. The development process should be steered by the conclusions of retrospectives, not by some management vision.

To be honest, the best places I worked at was where the manager was at the service of the team, relying on all the experts. Never the manager that thought he knew better than everyone else.
As a non-physicist, I found Jeffrey A. Barrett The Conceptual Foundations of Quantum Mechanics, Oxford UP 2019, quite interesting. It focuses on laying out the experimentally confirmed data that basically any theory and interpretation of QM must take into account and "explain" (unless there is something with the experiments or something groundbreaking new is found). It's understandable by laymen. However, at least my experience was that the more I read about QM, the weirder it appeared to me and the harder it was for me to grasp it conceptually.
I'm a big fan of F# as it has a huge company and ecosystem behind it. That said OCaml is where most of the language ideas came from. Much of what makes F# is owed to OCaml.
Having been a CTO (and not wanting to be one ever again): it is incredibly difficult to stay connected to technical details when being a CTO. To really feel and understand technical issues you need to write code. Not all code, but at least some, on a regular basis, encountering issues yourself. Fitting that into the schedule of a CTO is very difficult, as you will be expected to be on "management time", e.g. available at any time for any kind of meeting, chat, road trip, or phone/conference call. You can't set time aside for concentrated work.

And believe me, to be a good CTO, you do need to be connected to technical details and understand the tradeoffs. Just talking to other people who code is no substitute.

In my case, I decided I will never again want to be in a management position where I cannot spend a significant amount of time coding.
Surely the physicists are aware of such a trivial fact.

So the photon example is probably a simplification of the real example which does sort of work.
Yes and I'm saying that it doesn't hurt to just give them a pay raise after x amount of time, even if it's just a few percentages.
He only (recently) admitted to those two cases because he was publicly outed. It seems extremely unlikely that the only two times he was caught was also the only two times he cheated. I think it's very probable he has cheated dozens or hundreds of times and not been caught or not been publicly outed for it.
You can update copyright comments once a year.
I agree with the identification of these two attitudes, but I'd like to add they they are not mutually exclusive, or that one is strictly always more correct than the other.

In a slightly different light, I'd call the first attitude "academic" and the second "practical", without any particular positive or negative attributes.

They are both valuable and appropriate at the right times. This article is in the context of learning, and I do recall interactions with learners of both attitudes. Those embedded too strictly in either generally did worse than those who would think academically about a problem, approach it practically and evaluate it academically.

We have the strict "documentation tells this, and so therefore my code is correct" kind of adherence to the academic attitude, but when they lack the experience needed to fully understand the documentation, and are too rigid to do experimentation to validate their understanding..

We have the strict "but it works when I do that" but avoids referring to the documentation to try and understand WHY it works when you do that, and so miss out on opportunity to learn how to think up that solution without brute force.

Middle ground is way to go.. Read documentation, experiment to validate, analyze resulting solution to gain deeper understanding.
I believe RDS automatically stripes EBS volumes under the hood, but don't expose that information to you unless you enable enhanced metrics (it's shown under "Physical Device I/O", where you can infer the number of volumes in the stripe). I have no idea when the striping kicks in - presumable some specific volume size for gp2, or some provisioned IOPS setting.

According to the link below, provisioned IOPS tops out at 256000:

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_....
I guess it depends on who wins in November
In the short terms, Germans are rightly thinking "We'd rather get through the winter with local coal than pay Moscow" so no, this is not an environment benefit, yet.

However it is a good trend in longer term - I don't think that there is desire for a long term "turn back to coal", it's just short-term expedience until a better alternative can be built up - after all, those coal plants exist already. Yes it's done under difficult conditions now as a consequence of not doing it under good conditions earlier.
I was locked out of my 10+ year old google account for daring to use IMAP to access gmail from unknown networks and ignoring the "is this you?" emails for a while. I'd all but given up on it until I got a brand new Pixel a couple years back, I figured I'd try logging in with the last password I remembered working and it just worked, no complaints from the RFA. I guess the RFA requirements are completely dropped when logging in from a new phone to avoid people getting locked out as they're setting up their phone.
Install it in a virtual machine even though you say your laptop isn't powerful enough. Give it the minimal amount that it needs to do anything. Try to break the system. Do it! You don't learn unless you break things! If you're constantly scared of messing up or screwing up or doing the wrong thing or misconfiguring something then you're not going to be adventurous enough to learn.
Ok, zoomer.
Both uses of “begging the question” are common, and since the fallacy sense is invariably intransitive and the “raising the question” sense transitive (specifying the question as a direct object), they aren’t even ambiguous. As a bonus, the transitive sense also makes a convenient rationalization of the fallacy sense (which on its own is a iffy translation into non-current English of the Latin name of the fallacy), which can be seen as (despite very different etymology) being equivalent to the transitive sense with “what is the justification of the premise being discussed?” as the implicit object.

The pedantry that approves only the intransitive usage and rejects the transitive usage is silly on several levels.
Yeah, I admit that as a daily F# user I jealously look at some OCaml features.

For us the tooling + library ecosystem are more important to get sh* done.
If the supposed experimental conditions cannot plausibly occur in nature I don't think it's a valid thought experiment.
I recommend reading specs regularly when doing anything like this. Web specs are generally pretty approachable, and they generally match implementations very closely these days (largely because the implementers are the spec-writers, which wasn’t so much the case before, say, the HTMLL5 effort), with the caveat that parts of these drafts precede the implementations and thus may end up being altered due to implementation experience.
I wouldn't be surprised if this is because of the trip cap thing that Menlo Park has - which seems purely aimed at Facebook to collect tax revenue. https://almanacnews.com/news/2019/05/01/facing-trip-cap-slip...