HN user

cwills

34 karma
Posts0
Comments28
View on HN
No posts found.

Seems like this article conflates threads C# with asynchronous operations a little.

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.

My iOS device has never once shown me "this website requires Chrome." I get to use the mobile web without needing Google. And Apple is the only reason why.

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.

and she finds an issue in my product that I don't agree is a real vulnerability

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?

Not because it’s Apple, but rather because Apple are exploiting their position as iOS App Store gatekeepers to require developers to add Sign In With Apple. Mozilla don’t have this position / power.

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.

Doesnt make sense, if google didn’t geoblock EU IP addresses how would the EU react? Issue another fine which Google won’t pay?

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..

The problem is that when you are shopping for something, you don't want advertisers to be influencing what you see in search results. You generally want the best match to your search, not the product with the biggest advertisement budget behind it.

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.

We have a smallish team working on web apps and use a trunk-based-development branching strategy. Not really to do with helping CI/CD.

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...

Interesting. Following serial there was an interview with Jay by The Intercept where he talks about incosistencies in his story, and how lied about some details because he was drug dealing from his grandmothers house and he wanted to protect her from any fallout. https://theintercept.com/2014/12/29/exclusive-interview-jay-... https://theintercept.com/2014/12/30/exclusive-jay-part-2/

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. "

Is there any reason we cannot use both TypeScript and Flow.

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..

Does it bother anyone else that Go supports the GOTO statement? I would've thought GOTO an obvious construct to leave out when creating a new language, to protect programmers from themselves? (See Dijkstra on 'GOTO statement considered harmful')

Ok, I'll give some suggestions, I'll be blunt. But first you should know that I'm not a web designer - so take them with salt. It might also be worth asking for suggestions as a Hacker News thread? Or perhaps a web-design specific forum. I'm taking an interest because I think the web development world really needs a good site to serve as a list/index/catalog of open-source javascript (and css) libraries, with user ratings and comments etc.

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.

Looks more mature than JSDB.io - particularly with the larger collection of libraries and tagging system etc. But honestly your site is cluttered and ugly, JSDB is winning there. A twitter feed, really? I think your site needs some clear direction. Just saying.

I would argue that the self-documenting code in your first example (albeit excessively verbose to suite your argument) is better than having to put a comment above every terse statement one writes?.

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).

Couldn't agree more. The Yipit landing page may as well be asking for credit card details. Show your users some value before you rape of their email address - offer them something they want and they'll happily give you an email address. The goal isn't to collect a bunch of email addresses. It's to have active customers. You're losing potential customers by not showing what's on offer first.

Some of the ideas presented here look promising. But I really don't see this taking off in its current form. News and blog websites already wrap videos with the related written content and links etc. And as one user described above, clicking links half-way through a video really breaks the user's attention to the video. Perhaps it would be useful if YouTube used machine-intelligence to recognise the content of a video and provide links below to related Wikipedia entries or news articles?

Vim clutch 14 years ago

I think you're both arguing different things:

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.

Vim clutch 14 years ago

Trolling. Really? This guy is expressing an equally valid argument. And one that I suspect a fair portion of HN readers agree with. Personally, I thought it was April 1st when I saw a foot pedal for a text editor!? Accusing him of trolling is really lowest-common-denominator fanboi bullshit. He makes valid arguments, agree to disagree and move on.

Why I Left Google 14 years ago

"Pathological love for Java and anything resembling Java." "Java was viewed as being "good enough"; alternatives like Scala and Clojure were not considered."

Perhaps Google should have acquired Sun, and worked on updating Java to keep up with other C derivatives (e.g. C#).

Prevention is better than cure... So the next step would be to warn the developer before they make the code changes or during. Hooking into the IDE to visually indicate hot spots within the source file being edited on would be neat.