The number of monsters on the screen doesn't seem to affect playing speed for me, but when the wall of fire appears it slows down the game very noticeably. (Using Firefox on desktop.)
Just tried it and, apart from the UI being highly confusing (you just get a blank workspace basically, and it's unclear how to see other DBs and objects in them) it seems to have no support for PG schemas. When I did manage to connect to my DB it showed me the tables in the "public" schema only.
ah, sorry for the confusion. That's because the last 20 trades are excluded from the table/chart if you don't have the appropriate access level to view, in this case a Gold membership. That means when you are looking at the chart / table with starting year 2022 you are only seeing the trades up to 3/24/2023 instead of the present.
Exactly, but if you compare to the market, even though 5.7% absolute returns is a poor 15 month performance, much of the model's relative outperformance came from those 15 months where at the same point, the SPX was still highly negative
> This is a pay-per-call work and we need you to join as a interviewee (not interview candidates) for technical calls.
> Are you strong enough to pass technical interview?
> We will pay $100 for per call whether you pass the call or not, but hope you try your best to keep working with us.
I've never seen this kind of thing in a legitimate job at. It smells like a scam to get bank details, especially combined with the very generic description here and lack of any company details.
That is the second-shortest job application form I've ever seen. (The shortest one asked for a name, email and LinkedIn without a free-text field. I think "who are you" is more important than "name".)
Yea right! People seem to like it :) the last one I posted here got more than 200 applicants, many curious, great minds here. Could the job ad be connected with how companies are building product?
I like the brevity of it, but I don't like the assumption that every good candidate will have everything that they want to share with a prospective employer on their LinkedIn page. Something like "Link to resume, LinkedIn, GitHub, etc. (whatever you want to show us)" would be more inclusive.
When I first heard of the is-odd and is-even NPM packages I was sure they were a joke, yet there we are: 200K weekly downloads! Publishing the packages may have been the effort of one spammer, but many developers obviously chose to use them - that's the part that boggles my mind.
Well, look at one of the dependents: https://www.npmjs.com/package/handlebars-helpers - certainly a more useful npm package, but by the same author. Seldom do people actually type `npm install is-even` - there's just a jungle of transitive dependencies that can be traced back to one of jonschlinkert's many packages, which then circles back to something inane as `is-even` or `ansi-red`.
I once ran a simple grep in some of my node projects - most of them had a jonschlinkert package in node_modules, certainly not through any (direct) choice of my own.
What is a bit worrying though is that he is an active member and contributor to TC-39. Meaning that this kind of community hostility is very much alive among the people who rule JavaScript.
8 years later and despite much support for the `.node-version` file.
Someone else started using the .node-version file years ago, and because all open source packages won't form a committee to standardize this file, nvm will not support it.
They have a lot of hills. JS Private Properties was another.
Very often when I’m digging around GitHub Issues because of some bug or quirk or insanity in the JS ecosystem (which is often) I see someone spout the worst possible take - often being kind of a jerk about it - and when I look to see who’s responsible, very very often, ljharb’s name pops up. Often.
Dogpiling on someone deep in an HN comments tree isn’t exactly the classiest thing but…never having interacted with him myself, I’ve been harbouring this low-grade antipathy towards him - nothing unhealthy, just a groan whenever I see his name on GH - for years now, and it’s cathartic and almost gratifying, given his prominence in the community, to feel seen like this. Thank you.
I think we as a community really need to have a conversation about ljharb and his role in the future of our industry. If he was only a library maintainer, that would be one thing, we could just move on, find workarounds, alternatives, etc. But his involvement in TC-39 makes him one of our rulers in a non-democratic structure. That makes this different.
To be fair, the ESM switch has been botched beyond compare.
It’s like they didn’t want to become Python 2/3, and then did the absolute worst possible alternative.
It is beyond frustrating that it’s up to individual package authors whether or not their package supports ESM or CommonJS.
And yeah, it’s a pita when one of your downstream dependencies decides to go ESM only, and breaks your entire friggin chain of stuff that depends on it being CommonJS.
I agree. Mistakes were made and migration has been unnecessarily hard. This particular issue doesn’t even affect me. I simply turned off `no-unresolved`. TypeScript handles a lot better anyway (even with jsdoc type annotations).
But what is the issue here is the stubbornness of the maintainer and his unwillingness to accommodate a very sizable portion of his user base. The industry is moving on, and as a TC-39 member he should be aware of where the community is moving as well as show some empathy with his users.
I see, thanks. I guess that answers one question, but raises another: why have his packages depend on more of his packages? If his goal was to be included in as many node_modules directories as possible, and handlebars-helpers was already included what's the point of pulling in is-odd/is-even, too?
Might be this from his GitHub bio “Several years ago, just before my 40th birthday, I switched careers from sales, marketing and consulting to learn how to program” Good way to get more eyeballs…
He could sell rights to the repos and disavow any knowledge of its maintenance while maintaining the link in his own repos. When those sold rights are used to commit some crime he has plausible deniability as anyone else but got a payday. If you try spinning off the subpackage just prior to a sale then it shows some sort of intent.
I did learn one new thing from browsing the is-odd source code: Number.isSafeInteger(n) checks that n falls within the [Number.MIN_SAFE_INTEGER, Number.MAX_SAFE_INTEGER] interval.
...
if (!Number.isSafeInteger(n)) {
throw new Error('value exceeds maximum safe integer');
}
...
Given the lack of integers and my hesitancy to trust modulo for non-integer variables, I don't know if I would trust it. You would need to add some safety checks, but either you create an is_even/is_odd function that has safety checks, or you have to rely on developers adding in the checks anytime the number might have been in close proximity to a floating point number.
Something as simple as this can end up being neither even or odd.
I have not read the source but I had always assumed that this was the lovingly crafted effort of someone who is intimately familiar with the js standard making sure that some hypothetical expression like ![1] is neither odd nor even. Surely the idea that modulo is beyond developers is too horrifying to contemplate.
/*!
* is-odd <https://github.com/jonschlinkert/is-odd>
*
* Copyright (c) 2015-2017, Jon Schlinkert.
* Released under the MIT License.
*/
'use strict';
const isNumber = require('is-number');
module.exports = function isOdd(value) {
const n = Math.abs(value);
if (!isNumber(n)) {
throw new TypeError('expected a number');
}
if (!Number.isInteger(n)) {
throw new Error('expected an integer');
}
if (!Number.isSafeInteger(n)) {
throw new Error('value exceeds maximum safe integer');
}
return (n % 2) === 1;
};
It does some checking the `value` is an integer in the safe range, which doesn't even seem right to me. Why shouldn't you be able to call this on integers outside the save range?
Just want to say I really like the values on your careers page. Compassion and humility, but raising the bar at the same time. (Of course, it could all be complete corporate BS, for all I know, but I'd really like to believe it's not!) It's such a shame you switched from "remote (worldwide)" to "remote (North America)"!
Yeah, as hilarious as this is when it happens to a bad guy the really sad aspect of it, for me, is that their customer service experience is not so abnormal. If it were, most would immediately identify it as fake. Like, counting the numbers of nuts in a photo is a bit much, but we are so used to horrible CAPTHAs now that it's just plausible. Same with the phone menu, etc.
