1,671 karma · joined September 1, 2010
The RDSEED instruction is intended for seeding a software PRNG of arbitrary width, whereas the RDRAND is intended for applications that merely require high-quality random numbers.The solution would be something like:
1. Add a very simple form that sends you an email to the end of each guide. This isn't different from what you already have in your contact page but it encourages contacting you right when a particular guide is read.
2. Add, again at the end of each guide, a questions section. Format this in a way that could be similar to actual comments.
3. Every time you receive a question, you manually -yes, that means work, I know- add it as a new comment/pair of comments in that section and update the guide if necessary.
Advantages:
- Avoids spam on the site
- Single source of truth
- Encourages readers to contact
- Allows for easier filtering. Nothing gets on the site if you don't actually validate -and process- it.
Disadvantages:
- Still requires work from your part, though not as urgent as "live moderation".
- Does not completely feel like conversations. Doesn't let different readers directly answer each other.
- It may result in you getting spam in your email.
- It's not automated. Again: Nothing gets on the site if you don't actually validate -and process- it.
Neutral:
- Doesn't shift the site into a community. I point this as neutral because it isn't bad per se but I understand that you do not want that.
I've seen this sort of set up work mostly fine. It does require work from your part, I repeat, but that really depends on how well it works -how much feedback you get- and since you seem to want that feedback to update the site, then the effort should be worth it.
If you go this route, one recommendation: In that simple contact form, set the action to something like mailto:contact@allaboutberlin.com?subject=... and include some identifier in the subject that easily links it to the specific guide they're sending it from.
You just throw your random question, regardless of any possible merits or validity, without really making any argument at all. How can you expect to engage anyone's attention at all if you fail to make any effort yourself?
And that's not even mentioning what bell-cot's link points out.
The end result is poorer content and less variety.
It may well be just my impression though.
---
Other than that I don't know what exactly you mean by "their content within the sections" or what are you correlating to the rank.
So, for slickytail and anyone who has the same question:
The code is actually compressed into a binary blob. You can see it if you just look at the source of https://0b5vr.com/0mix/0mix.html
A small script loads the blob and uncompresses it before running it through eval:
fetch("#").then(t=>t.blob()).then(t=>new Response(t.slice(156).stream().pipeThrough(new DecompressionStream("deflate"))).text()).then(eval)
This is a common approach in browser demos and what is counted as "less than 64Kb" is that final html. A similar technique compresses it into a PNG.- One submission 19 days ago. https://news.ycombinator.com/item?id=44879608 This is clearly promotional.
- A previous one 4 days before that https://news.ycombinator.com/item?id=44839405 which is a blog post. It also has a single comment and it's from rkwap (In their bio: "Building http://huntyourtribe.com" and the account has no submissions and only this single comment).
So your submissions are clearly marketing and promotional. This isn't bad in itself; people are allowed to submit their own projects. It's also not a problem to say things like "new and novel approach", though I must say that it sounds exactly like an advertisement.
But the problem is that there's an important guideline [0] on HN that says:
Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity.
You are not posting "your own stuff part of the time". You are posting only your stuff, which is considered self-promotion and is not the focus of HN.[0] The guidelines are here: https://news.ycombinator.com/newsguidelines.html
To be frank, no. That is too much to ask.
The overview, as explained in another comment, fails to be convincing. And you're asking people to spend time and code something up when it isn't even clear if your framework has any real and convincing advantages.
It is you who should create that first working example, which someone can then tinker with and modify.
The README should have one -two, at most- simple but representative and complete example. An example that shows actual usage of something simple enough to be small. See the examples I suggested above. As a companion to that, you can put that same code in JSFiddle and link to it in the README, but keep both the code and link in the README.
As for the documentation, what I said is that the code shown should always be good code, code where names make sense. You may or may not make the effort of putting full JSFiddle examples into your documentation, but the code that you put in the docs should use meaningful names.
That's a guide and so it has more details. What I was saying is that the README, in a way, needs less details.
Also, that guide still makes the same mistake of using generic examples and names. It's full of foo, 'bar', someOtherEvent, First.onConnect('something', 'here').handle(arg1, arg2), etc and that's not really how you should write documentation.
So what shouldn't be there? Well, most of it. You don't need a whole section of "Advantages over other frameworks" and then a table comparing to other frameworks.
You don't need most of the overview you have. Just picking something random: there's a full table with methods of Q.event. These are details; it's simply too much information that is not helpful to someone who wants a general overview of your project. The same can be said for most of the stuff there. The section on templates is useless for a README: It shows some very specific details (like the fact that there's a Q.Template.load.options.dir) without actually showing a real-world example, because foo, bar, baz, Some/name, and the code actually shown is all synthetic and abstract.
And that's the other problem: It's generic info. And so we get to what the README is missing: A simple, complete, minimal, working example.
And, yes, you end up the README with "Putting it all together", I know. But again, it's an abstract and generic thing. It shows a bunch of code ideas just thrown together for the shake of showing them. Even the comments in that code say things like "you could do this", "you could do that". It doesn't really help.
What you really need is something like a counter and two buttons to increment/decrement, or an input box and a list that gets filtered as you type, or whatever. Something silly and small... but complete and working. You don't need to show off all the features in that example. Just make sure that the code in the example clearly represents the typical way you'd write it and that you can hopefully keep it under 20-25 lines. Make it so simple and self-explanatory that you don't need to add many comments or any at all if possible. Ideally, make it so that you can actually just put that code into CodePen/JSFiddle/JSBin/CodeSandbox/Plunker/WhateverYouPrefer and then link it with "See this example live".
Again, it won't show all the features available and that is fine. But it will give the reader a fairly good idea of the general approach and the feel of using your framework. Because right now, with so much information the README gives a feeling that your framework it's anything but small, that is something complex with lots of abstract options and ways of doing things.
Here's the latest thread from the start of this month: https://news.ycombinator.com/item?id=44757793
There are other brands, of course; Pentel has a similar marker and some other smaller brands too. I just think the Tombow is very nice and easy enough to find.
These pens are sort of the modern version of the Japanese calligraphy brush, so they're nice for writing but much more practical.
My equipments
Video editing: Final Cut Pro XOne small quirk/bug:
1. Browse all ( https://www.cancateat.food/search ). There are 174 results found in "All foods".
2. Go on to page 2.
3. Now click on a smaller category, like Diary. There are 7 results found in that category... but you can't see any.
The problem is the pager remains on page 2 when clicking a category. "Page 2 in Diary" is empty because there aren't enough results to fill a second page. Not only that, but the pager is actually hidden if the number of results is less than one page. So you get "7 results" but you can't see them and you can't page back down.
I'd guess you need to reset page back to 1 whenever you click a category.
Admittedly it's not a hi-end phone. I use a Moto G7. Screen is 1080x2270 at 6.2 inches according to [ https://www.gsmarena.com/motorola_moto_g7-9357.php#eu ]
Trying it again to verify... You're right that it's the width. I get a small-ish horizontal scroll. But the problem is that no matter if I scroll it completely to that side the left still gets cut off.
Offtopic but rewarding your article on Firefox on Android, there's a slight misalignment on the side. The left side gets cut off about 5-8 pixels, I'd say. It cuts off most of the first letter on every line.
It might be just my phone, of course. But I don't have any particular extensions installed or anything else.