It's also one of the best shareware models ( Is this even a word these days? ), that I've ever stumbled upon.
Keep up the good work, folks!
> which day to day tech workers working on internal B2B do not face
That's so true. Good luck explaining to management that the front-end app needs additional cloud resources, such as a server, so we are on the edge of the trend with SSR.
Most apps behind a login face tough architectural / security meetings, defending SSR for their use-case.
When I first read the news, I thought about another hit for the crypto, however looking at what happens I’m a bit worried where will the avalanche reach next Monday.
Stay safe folks!
Seems like it’s not an electron app, but also works with JS and even React.
In case someone is using both. What are the Pro/Cons against Raycast for ScriptKit?
Now it's really hard to argue with architects / developers why cookie authentication / bearer token makes more sense than JWTs.
This makes no benefits as to bearer token or any random string that the server "knows" is a valid authenticated request via internal store, like a DB.
Eating sugar for example in excessive amounts leads to way worse diseases - https://www.webmd.com/diabetes/features/how-sugar-affects-yo....
I find it excellent and definitely a helpful tool to think about when you are struggling with type safety vs runtime data.
I think they do that mostly because for the users who’ll have to download the header 100 times for each action they’ll do. Not really sure that all benefits from SPA are hidden in company costs. Mostly they are in modern tech approach.
Writing this I still agree with the article. SPA is needed when you are under authentication but publicly you can live with progressive web.
https://github.com/h5bp/html5-boilerplate/blob/master/src/in...
Mentioning corona here, I think the society is desperate to find more IT folks around and loosing someone because of shitty interview process ( which I mostly skip because I’m a freelancer ) is quite sad.
I have a 10 months old daughter and it's getting tougher than ever. We are living outside of "grandmas" location, so we're definitely struggling with focusing on something else than our baby. I took some holidays now, but it seems that the most I can do is relax from taking care of the baby.Do you know any good books on that matter?
I remember having similar struggles with infinite-scroll product page a while back ( ~5 years ago ), with variable card height. I thought this could be done with CSS nowadays, but I guess css grid & flex-box specs don't go that far.
Awesome work!
Isn't this possible with only CSS?
I see each article ( section ) with position absolute and heavy JS calculations. My browser brain thinks that with some combo of flex-box / flex-wrap and breakpoints you could achieve this without the need for resize handler. I guess that's not the truth
So can you point the struggles not doing this with CSS?
> Here, we change the engine type from turbofan to propfan. Just to test how it works. Since the new engine no longer matches our snapshot, the test fails. We’ve got a report, and our engineers are on their way to investigate the problem.
I would be really happy if I know that the onboard computer has tests that checks if the engine being used is compatible before it takes off.
IMO, tests in general should be as close as possible to the real use-case ( kudos for the screenshot testing ) and as far as possible from the implementation. What happens with snapshots is that you are bound to the implementation. Maybe I have a logic somewhere in my code that does s/propfan/turbofan/. Would a user be interested in that or the functionality itself?
We ditched all JEST's snapshots statements in our code-base, because of code-coverage abuse and false sense of "being safe" just a couple of months ago. It was a good decision that helped us be closer to "what the user sees" rather than "what the markup should be"
> curl https://aviary.sh/install | sudo bash
I would really try to avoid this, especially when it's targeted for sysadmins ( I guess DevOps nowadays ).
What's the big deal of having this instead :
> $ wget https://gitlab.com/dchester/aviary.sh/-/archive/1.3.2/aviary...
> ./aviary-install.sh
> Here’s the simplest solution I could come up with:
> 1. Serve the current site from a subdomain (e.g., 2017.ar.al)
> 2. Make my 404s into 302s that point to the previous version of the site.
> 3. If I change the site again in the future, rinse and repeat.
> I call the technique 404 to 302.
const isFalsy = require("is-falsy");
const isObject = require("is-object");
const isFunction = require( "is-function" );
const hasThen = require( "has-then" );
function isPromise(obj) {
return !isFalsy(obj) && ( isObject(obj) || isFunction(obj) ) && hasThen( obj );
}