cwills
The way I see it, threads are for parallel & concurrent execution of CPU-bound workloads, across multiple CPU cores. And typically use Task Parallel Library. Async/await won’t help here.
Whereas async/await for IO bound workloads, and freeing up the current CPU thread until the IO operation finishes. As mentioned, syntactic sugar on top of older callback-based asynchronous APIs.
Let's be real though, Apple didn't enforce this to save user's the small annoyance of 'use browser X' popups. Instead it gives them full control over what web APIs are available on iOS devices, so they can avoid implementing those APIs that would impact on their App Store revenue. They have a clear financial benefit in not supporting the PWA technology that would move the 'simpler' apps off their app store and into web - where they wouldn't receive their developer license fees, a cut of paid apps and a cut of paid subscription fees (outrageous). Also, I believe it was Steve Jobs who first shared the vision of web applications on iPhone “that look exactly and behave exactly like native apps” ?
> Instead it's web developers, who are just annoyed that they have to actually respect the conventions of the platform they're building for.
Developers already get around this to some extent with cross platform tools such as React Native, Xamarin, Flutter. Native apps will always have a place, PWAs are not going to replace sufficiently complex app experiences, much like on Android or Windows.
If it’s not a real vulnerability then why would it matter if she publicised it?
Or, is it actually a real vulnerability but you don’t want to admit it because she (the security consultant) is getting paid per vulnerability found?
I think people would have the same issue if Google required ‘Sign In With Google’ in play store apps that have Facebook login, and returned throwaway / proxies email addresses.
There by, when apple passes a [email protected] address back, it won't match the existing account's email address = Sorry, matching account not found ?
A similar analogy would be like the US blocking their citizens from traveling to North Korea. But then having direct flights from LA to Pyongyang and expecting North Korea to enforce the ban of US citizens at their customs. It’s not their responsibility..
So they should remove advertising from google search results altogether?
Like saying TV networks shouldn't put ads/product-placements in their shows because their viewers are only interested in the shows/content.
The advantage we see is that new developers can start developing as soon as they clone the repository, without needing to switch to the 'development' branch. This is particularly useful when on boarding new developers who are inexperienced with Git. I found that when using Git Flow that the (stable) master branch frequently ends up out-of-date when developers are required to remember to merge into it releases into it.
Diagram of our branching strategy: https://gist.github.com/CameronWills/abf9e307669b1005c88ef82...
I find his response to this question compelling when talking about Sarah Koenig and Serial:
" Was the name ‘Serial’ ever used?
No. Not to my recollection. She kept saying ‘This American Life,’ ‘the radio,’ and ‘a documentary.’ There was no talk of ‘Serial’ or a podcast. Then I asked her outright, ‘Are you an advocate for Adnan?’ She said ‘No,’ that she wasn’t his advocate. But she said that she had talked to Adnan, and she wanted to get more information about the case. She said there was new evidence, and I said there’s no new evidence that’s gonna change what I saw: I saw Hae dead in the trunk of the car. If Adnan wants to take the stand now and explain that away, let him. But there’s no evidence that’s gonna change what I saw. I don’t know how she was murdered, I don’t know exactly how she got put in that trunk, and I told the cops that. If Koenig wants to get into how that all happened she can go there. But that doesn’t change what I saw. And that’s the only time I commented directly on the case to her. "
Besides perhaps the extra 'compile' time added to do both translation with TypeScript and then static analysis with Flow. Both tools have their advantages and disadvantages.
May as well throw in a linting tool as well..
Fundamentally, I think the intent of your design is wrong. Its cluttered and all about the bells and whistles rather than focusing on use-cases and the problems your site should be trying to solve.
(1) Home page Editor's Choice Part Get rid of this, I don't think users care about your editors picks. User's care more what the user base / crowd thinks. So you could perhaps put trending libraries (those receiving a lot of up-votes recently) here instead. Or otherwise just remove it all-together.
Blog Part Also get rid of this. The foremost parts of your homepage should be the Category list and a search box. Also get rid of the tag cloud - doesn't add anything IMO.
Layout and Color Scheme All wrong, too many different colors and shades, jagged lines and shadows everywhere. Less is more here I think.
(2) Category Page Layout Change to a list-view instead of a grid-view. The grid looks too squashed, and users don't mind scrolling - list view is better for responsive design / mobile devices. Also sort the list by rating.
Each Library Increase the font size of the description <- will work better when you change to a list view instead of a grid. Show the rating larger as well, and then to a lesser extent the GitHub stars etc. Take some design pointers from the StackOverflow question list (http://stackoverflow.com/unanswered).
(3) Library Page Comments Shift the DISQUS comments above the 'ALSO ON JSTER' part, put that stuff at the bottom, users care more about comments. Remove the 'RECOMMENDED CONTENT' - its irrelevant and your site is too immature for advertising yet.
Rating System Light bulbs? I honestly think you would be better off with an up/down vote rating system like StackOverflow. A library having a 5/5 rating doesn't mean anything when there is only one vote (probably from the developer who wrote it and submitted the library). If you wanted to make it really smart, you could allow users to up/down vote a library for specific category. For example, users could up-vote the D3.js library within the 'Charting' tag/category only if they wish to - which means the user thinks D3.js is good for charts.
That's all for now - have run out of time.
Programming with descriptive and meaningful variable / function names that have intrinsic meaning skips this step: 'wait, what was the cg2 again? let me waste time by looking back through the code and figuring that out again'. Particularly for others reading your code later.
But I try to fit somewhere in between the two examples you've shown, meaningful but not too long -> the benefits of longer variable / functions names diminishes when names get too long as variable names tend to blend together (see law of diminishing returns).
jlgreco: vi/vim is an efficient text editor when you learn it! And even more efficient with a foot pedal! Don't discredit our time spent learning vi/vim when it is in fact an efficient text editor!
robomartin: vi/vim may be an efficient text editor, but in the grand scheme of a large(non-trivial) project, small improvements to text editing efficiency are irrelevant. Particularly at the sake or cost of learning and mastering vi/vim. There are easier-to-learn and more-intuitive text editors available now.
Both valid points.
Perhaps Google should have acquired Sun, and worked on updating Java to keep up with other C derivatives (e.g. C#).