Hacker Newsnew | past | comments | ask | show | jobs | submit | mrswag's commentslogin

FM works, and doesn't need any addition when you increase the number of listeners. I don't get it. Why throw away millions of perfectly fine radios?


Digital is more narrow and compact and allows more efficient use of the spectrum in general. More transmissions, different uses, sharing, freeing space up for other allocations, etc. All of that is resource/demand driven. More people is more demand.


While DAB transmission is more efficient than FM, the receivers are more complex and draw more power than FM receivers. I'm not sure the tradeoff is right in this case.


I get that argument for tv transmission, but the FM bandwidth is tiny by comparison, so just doesn't seem to justify the switching pain (particularly regarding cars)


I'm genuinely wondering: is pair programming better, compared to doing the design in pair, going to work on your own, then reviewing each other's code?

As an introvert I don't think I could handle the "pair all day" approach.


> is pair programming better, compared to doing the design in pair, going to work on your own, then reviewing each other's code?

The literature is, I believe, pretty thin and equivocal. However the suspicion is that pair programming is pretty much the core loop of bouncing back and forth, reduced to the smallest possible size.

It also avoids some of the antipatterns I've seen with code reviews -- widely distributed patches, reviews getting stale because they were too hard for a Monday, then a Tuesday... then a Friday ...

> As an introvert I don't think I could handle the "pair all day" approach.

You can take a break if you need one. Lunchtime is fixed at an hour. I typically go and spend it alone with a book.

There is sometimes a confusion between intro/extraversion and sociability. I'm quite sociable, I genuinely like talking to people, but it drains me because I lean towards introverted. So the lunchtime recharge is very helpful.

Each pair finds their own balance.


I guess it keeps you honest.... e.g focused and ontrak


I generate static webpages from markdown in a < 100 lines bash script. It's just a for loop using sed, pygments and markdown, hosted on github.

It has a local webserver, spell check, optional image compression, and minimal dependencies.

I don't get the need of Jekyll or Hugo. They're bloated and it's a pain to customize so called "themes". I'm OK with 'boring' HTML and CSS.


It's great you built your own tool and workflow that suits you, but there's no need to declare things 'bloated', just because they include things you don't want to use. That's your opinion. Its defaults suit me pretty well, and it's really well documented.


Bad wording on my side, sorry. My grief is mostly against some prominent themes that weight 5 MB a page, and feature jQuery to animate the menu.


Cool, I hear you but Jekyll actually comes with a very minimal theme (when you 'jekyll new my-site'). Heavy 3rd party themes aren't really the fault of Jekyll.


What do you use for the local webserver, spell check and image image compression?


`python -m SimpleHTTPServer` for the local server (or if you prefer the python3 variant, `python3 -m http.server`), aspell for the spell check, and OptiPNG for PNG compression.

I didn't found something (yet) for JPEG.


> I didn't found something (yet) for JPEG.

jpegoptim --strip-all


Thanks, exactly what I was looking for!


+1 for Hugo.


The graphics are misleading, the Y axis is stretched to make the change look big.


If it's significant then what's wrong with using a scale that reflects that, even if the numbers are small in absolute terms?


In this case at least, they're going from a peak of ~1.66 posts/day to a valley of ~1.54. As an aggregate that looks like a compelling pattern, but consider it on an individual level: we're talking about one post every ten days. Initially looking at the graph made me think the difference was way greater than a post every ten days, so I'd agree with the GP that it is misleading; I was mislead.


Yeah, but if one post every ten days really is predictive, then showing it at a larger scale isn't helpful.


Looking at the graph, it seems like we're talking about ~16.5 posts in the ten days before a relationship versions versus ~15.7 in the ten days after. In the context of an individual, Facebook might be able to combine this with a bunch of other data to make guesses about people entering relationships, but a quick look at the graph makes it look like they could do it from just this one piece of data.

FWIW, I think people are often too quick to dismiss graphs as misleading due to the y-scale and I do think the graph is interesting. That said, I think a lot depends on the context, and being directly below "When You [emphasis added] Fall in Love, This Is What Facebook Sees" makes this seem misleading.


this is such a classic way.


[flagged]


"Fake news" seems to mean different things to different people. What do you mean by it? That it's not important? That it's just entertainment? That it's false? That it's propaganda? That the person posting it here is doing so for some nefarious reason? Something else?


I would say he uses it like everyone else - for any news/source they don't agree with.


It has a nice GUI frontend with useful presets, understandable for the layman. Very good tool for the people not too versed in CLI and/or video formats.


Queue management (really great). Ability to extract titles from DVDs.


Does a coverage-guided QuickCheck exists, à la AFL? AFL is really good at finding deeper code path that the randomness only approach might not find.


I looked into this while making RamFuzz[1], but parameter generation (QuickCheck) is quite different from input-blob evolution (AFL). It wasn't clear to me how best to leverage a parameter mutation that happens to increase coverage. Ultimately, I decided that random generation (without guidance by coverage) coupled with AI classification of test outcomes is the most interesting approach.

[1] https://github.com/dekimir/RamFuzz


The bottom line is the power consumption. A big fat i7 (desktop) can draw 91W, while a fanless, battery operated smartphone can pull from 5 to 10W.

Power optimization come at a performance cost.


It's cheaper than that. A HackRF and some sort of better clock and you're done.

http://www.rtl-sdr.com/cheating-at-pokemon-go-with-a-hackrf-...


This censorship show that you don't even begin to understand the problem.

This list could prevent people from getting their card skimmed, and you take it down.

I'm moving away from gitlab.


To where?

I have to confess, when GH did something offensive I did cancel my paid account there but I still use it, so I guess I didn't care that strongly about it after all...


I use a simple bash script[1] to paste together html headers and markdown files processed by python-markdown.

The resulting .html is pushed with the source to the github repo. This setup, while not very sexy, doesn't even need a CI.

[1] http://toastedcornflakes.github.io/generate.sh


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: