Have fun, don't waste these years worrying about the future, you'll get plenty of time in the next 50/60 years to do that but you'll never get your youth back.
Readit Newsinteresthrow2 commented on Ask HN: How can I make the most out of high school? · Posted by u/TheAsprngHacker
Deleted Comment
interesthrow2 commented on Star Citizen: The Road to Release, Financials and New Partners cloudimperiumgames.com/bl... · Posted by u/doener
They might be talking about non-monetary resources, like partnerships and experience?
Robert is an industry veteran. And his business hired most of Crytek staff in Europe, did you play Crysis series? Do you really believe its developers lack "experience"?
interesthrow2 commented on JavaScript Getter-Setter Pyramid staltz.com/javascript-get... · Posted by u/adgasf
I'm interested in this simple closure code from the article:
function getGetNext() {
let i = 2;
return function getNext() {
const next = i;
i = i * 2;
return next;
}
}
function getGetNext() {
let i = 2;
return function() {
const next = i;
i = i * 2;
return next;
}
}Or as an alternative one can use a generator, they are built for that purpose AND are supported by a wide range of other JS constructs without any need to create iterators manually and all that.
function * getNext(){
let i = 2;
while(true){
i = i * 2;
yield i;
}
}
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guid...
Deleted Comment
Deleted Comment
I assume your criticism applies to OO? Or functional programming? Or event sourcing? Or any number of programming concepts without a "standard"?
> I assume your criticism applies to OO? Or functional programming? Or event sourcing? Or any number of programming concepts without a "standard"?
Don't assume anything, I never talked about OO, or functional programming, or event sourcing or any number of programming concepts without a "standard". Don't make up things in an attempt to further whatever point you are trying to make here. I never talked about those things and don't care about them.
Deleted Comment
It sucks because it's not a spec, that's all. HTTP is, GraphQL is. When implementing GraphQL either you follow the spec or it is not GraphQL. Same for HTTP. An vague idea shouldn't be the basis for architectural choices and I'm glad REST and its legacy are now criticized and contested.
Deleted Comment