skysight-inc/HackerNews huggingface dataset:
Location: India

Remote: Yes

Willing to relocate: No

Technologies/Skills:

- UI/UX design for web, iOS and Android

- Information architecture

- Interaction design

- Visual design

- Icon design

- Branding

- HTML & CSS

Portfolio: http://radesign.in/portfolio

Blog: http://radesign.in/blog

Email: http://radesign.in/contact
I'm a web and mobile designer SEEKING WORK

Experience: 5 years

Technologies/Skills:

- UI/UX design for web, iOS and Android

- Information architecture

- Interaction design

- Visual design

- Icon design

- Branding

- HTML & CSS

Location: India

Remote work: Yes (only remote; no onsite)

Portfolio: http://radesign.in/portfolio

Blog: http://radesign.in/blog

Email: http://radesign.in/contact
I agree with that. My problem with whiteboarding is you almost never do that in the course of your daily work. The idea was about introducing more of what we do in the course of a typical day in the interview process.
Forgetting ads forever
People with experience in the field have been telling me I am a very good programmer. I always compare myself to the car mechanic who holds a screwdriver to the engine, puts his ear on it, and immediately hears that the third valve needs replacement.
I have some doubts about the usefulness of the water usage numbers given. Most of the water plants and animals take in is not retained long term or used in chemical reactions that break down the water. It mostly ends up being released by the organism back into the environment.
Familiarity, curiosity and not even realizing that the firmware from Shibby runs on the GL are some of the reasons. Besides that there's customers running on DD-WRT so it is good to have at least one form of it running inhouse. Those customers are not on the mini nor on a GL, but there it works and in that case cross flashing remote routers is something I'd rather not do.
I'd be proud to be a 1.3x-er
Google Maglev: 2008

XDP (Facebook and others): 2016
CppCon 2015: “Grill the Committee” (video, 91min)
When hiring contractors the company doesn't have to pay any of these things (it's on the contractor). I'm currently contracting for a company in Italy and getting much more than 3k/mo.
Well, Feynman is assuming that x^n + y^n is as likely as any other number to be an nth power. He shows that under this assumption, FLT is very likely true. So if FLT is false, it probably wouldn't be due to some coincidental counterexample. There would have to be a mathematical structure forcing x^n + y^n to be an nth power in some cases. In your example, the mathematical structure forcing x^n to be an nth power is obvious.

The downside of Feynman's approach is that it can't get you any intuition about the structure, the things that aren't statistical randomness. And whether FLT was true or false depended exactly on whether the structure pointed one way or the other. So I have no idea why he was so confident in this analysis.
PhotoKey 7.0.16117 Pro Crack Incl Serial Key
I work in the netherlands and I bill $125/hr.
I've only poked at the FreeBSD TCP stack and not the Linux stack, but it seems like if the problem is locking, you should be able to get good results from working on the locking (finer grained locks / tweaking parameters) in less time than building a full tcp stack.

What kind of limitations are people seeing with the Linux kernel? If I'm interpreting Netflix's paper[1] correctly, they could push at least 20 Gbps of unencrypted content with a single socket E5-2650L (document isn't super clear though, it says they were designed for 40Gbps). My servers usually run out of application CPU before they run out of network -- but I've run some of them up to 10Gbps without a lot of tuning.

[1] https://people.freebsd.org/~rrs/asiabsd_2015_tls.pdf Context is accelerating https downloads, but some decent numbers anyway.
The comment from bertilda-lovejoy just summarizes the first-world problems very well.
> Since ARM moved to ARMv8, I groaningly refer to v8 as "x86 v2"

I'll have to disagree, I think ARM mostly did the right thing with the A64 instruction set. The AArch32 instruction sets were just getting ridiculous (just having multiple instruction sets for one architecture is pretty messed up), with A32, T32 and a bunch of other extensions (ThumbEE, Jazelle) which pretty much no one used. In addition, the A32 and T32 instruction sets have grown organically over time, with new instructions being crammed in any unused / invalid space, which is how we ended up with one encoding doing this one thing, except if one register is the SP or PC, then that is a whole other instruction or with immediate values being split up over 2, 3, 4 fields. Also, a few features had turned out to be pretty bad ideas: for example access to the PC as a general purpose register is overly complicated to implement in OOO cores (verification cost) and comes with performance penalties, but it still had to be supported; the IT instruction is another fun one, especially in the context of dealing with exceptions.

A64 pretty much takes the set of instructions which has emerged over time, removes the bits which are not suitable any more or were bad ideas in retrospect, fits them cleanly in a new encoding space and removes some of the flexibility which was getting in the way (e.g. VFP having either 16 or 32 double precision registers). I expect AArch32 to be gone from most high performance implementations in a few years, with a software DBT option remaining available for legacy software which still hasn't been ported, which is when the implementers will be able to fully benefit from having a simplified AArch64 compared to AArch32.
I don't think parent commenter was saying it's not a problem, just that it's a pretty universal problem.
> "Please don't rewrite your network stack unless you can afford to dedicate a team to support it full time."

Generally agreed but there's a caveat to this statement.

> "Twice in my career I have been on teams where we decided to rewrite IP or TCP stacks."

This is the caveat. Don't try to rewrite a protocol that's already running billions of devices on the internet which you have to interoperate with. It's a much more tractable problem when you control both ends.

Twice in my career, I've worked on protocols (with success... the first company went public, second has it's protocol working well in millions of devices). Both times, the protocols were key to the business of course and both times the "custom" protocol only had to interoperate against itself on the other end.
Hubble captures polar lights on jupiter
Apple hired the President of the health company Sage Bionetworks
How to get Timezone ID's in C#
Well I agree that it is wrong simply because it breaks (for example) the PNG standard:

"RGB samples represent calibrated colour information if the colour space is indicated (by gAMA and cHRM, or sRGB, or iCCP) or uncalibrated device-dependent colour if not."

So webkit shouldn't try to transform the colors to sRGB but simply display it according to whatever display is present.

Having said that sRGB designed to be consistent and not high quality. It even has a "black point" defined, but nobody respects that since it would cause a maximum contrast ratio for all images represented in sRGB.
Das Keyboard is crowdfunding a cloud-connected mechanical keyboard
> have a hard time procuring a large compensation package employed as a software engineer in a utility company

in which case, there ought to be market pressure for software engineers to move away from such companies. When the company finds out they actually need a good programmer, they end up having to pay more again for quality (perhaps, indirectly, via consulting companies). But the current anecdotal evidence is that those companies _can_ pay very little, and yet, no catastrophe has happened. The only valid business conclusion is that the highly paid engineers aren't needed there!
Another spaniard here, and I can confirm that it absolutely is a problem of not wanting to pay appropriate wages.

First, most software companies only offer crappy jobs that don't require specific skills. Most of the job postings are for standard developing positions in very common languages such as Java or Python. Considering how many people finish their degree or their FP (Formación Profesional, courses of about two years oriented towards the job market, and often including internships) each year, and how high the unemplyment rate is, I just don't believe that there aren't enough applicants.

Second, a lot of the big companies are what we call cárnicas (roughly, "butcheries"), i.e. companies specialized in outsourcing that pay ridiculous wages (10K a year for an entry level, full-time position where you will get fired if you don't do three hours of overtime a day is not difficult to find). Most developers know better and stay away from these, but because of the unemployment rate, a lot of people end in these places.

In other words, those hard-sought qualifications are more or less "will do a specialized job while getting peanuts in return". The article misleads by giving an example of a position with a 200k salary (which I'm also very skeptical of, like gutnor), and fails to mention that it's a very specific position and does not represent the whole set.

The only way I could believe that there is an actual shortage of workers, and I still doubt that it's true, is if we took into account that many of the good developers fled to greener pastures a lot of time ago.

EDIT: I should also mention that the problem is not that there isn't money and therefore the job market can only offer crappy jobs. On the contrary, most of the big enterprises and especially the cárnicas are very lucrative for their owners. The problem is that there is a very big barrier entry, because these companies strive on public contracts, and because of corruption, new and smaller companies can't stand a chance against the already existing ones.
Therein lies the rub. In most other countries business people who have to deal with subtle business requirements speak English decently well where in Spanish business it's absolutely normal for a CEO of an international company to only speak broken English at best.
This way of estimating a dev's likely productivity would operate independent of their individual ability, as well as be applicable across all worker categories. For example a dairy farmer in Switzerland earns more than one in Poland because people pay more for milk products in Switzerland compared to Poland.

So why would the GDP per capita of their country be a useful tool in deciding who to hire?
Sharing CPU resources between user space drivers is certainly a challenge. The best way to view this is that the kernel provides a general purpose solution for sharing resources with some associated overhead. Tools like DPDK and SPDK let you opt out of that, but now you are responsible for intelligently sharing the hardware.

You, as the application developer, have a distinct advantage though - you only need to solve the problem for your application, and using that knowledge can often lead to more efficient solutions. This may mean dedicating cores to the network or disk, or it may mean working in fixed sized batches, etc.
I haven't yet run into a case where it makes sense to do it, but you can gain some efficiency because you avoid context switching between the kernel and the program.
Shouldn't PBS programming be... erm... publicly... available?

I have the impression their charter mandates them to operate for a public good and it eludes me how allowing a single company have a digital distribution monopoly on its... public programming furthers that goal.
Fair point but it doesn't debate the merits of vegetarianism. I eat meat. I am somewhat uncomfortable with it.
Location: Philadelphia metro region

Remote: Yes

Willing to relocate: Yes

Technologies: Linux, Python, Django, PostgreSQL, Vagrant, HTML/CSS, bash/zsh, AWS, Docker, Git, SSH. I am currently learning JavaScript.

Résumé/CV: on request

Email: wyclif@gmail.com

I'm currently looking for entry-level or junior dev work. While I'm a generalist with both front and backend and will happily accept work on either end, I am most interested in DevOps and backend. I'm comfortable on the CLI and with vim, tmux, git, ssh, etc. I also have some sysadmin experience. Excellent soft skills, and I'm easily in the 99th percentile of English fluency and written communication. If you need good documentation, technical writing, or even web copy, I can definitely help you with that if you're willing to provide some mentoring and/or certification to help me improve my programming chops and technical development. I thrive on being a details guy and a quick learner. Shoot me a message—I'm hungry to level up.
You can do zero copy I/O on Linux using vmsplice+extensions, and on FreeBSD using regular read/write calls. Both can do DMA with user space buffers with much less disruption to traditional design patterns for implementing network daemons.

I think the real benefit of DPDK and netmap is that you're avoiding all the logic of the existing IP stacks, not to mention firewall rules, etc. At the same time you're now responsible for all of that. And IMO the amazing throughput most people claim to see with DPDK is a result of simply neglecting to implement all the hard logic which makes the Internet actually work. All the weirdness, head scratching, and hair pulling these solutions cause is an externality engineers will never care about, and in most cases probably be oblivious about. The exception to this state of affairs is when they're doing read-only packet sniffing and filtering, simply passing the packets back out another interface.

If most of what you care about is avoiding the cost of the kernel/userspace split, then you can just use NetBSD Rump or similar unikernel frameworks.
This is where supported distributions come in. In Debian or Red Hat you can
practically assume that the OS update will not break anything. (There are
occasions where it does break something, but I don't remember anything major
in a good few years.)
That's a well known troll account.

Edit: New to GitHub I guess, but that name is well known on other sites.
Free hi-res CC0 licensed images from India
...and then good luck when the application that yesterday worked well today
doesn't work at all, because somebody removed a small function critical to
your workflow and you can't get it back. Seamless experience!
So pointing out hypocrisy and tainted credibility is not allowed on HN. I see. Neckbeard logical fallacy # 82
The full rule

> Payment is for digital content that may be consumed outside of the app itself (e.g. songs that can be played on other music players).

As Spotify music can be used outside the Goole Play app, Google doesn't take a cute.

The same reason I can buy Kindle ebooks within the Android app
Compulsory voting is actually pretty popular over here in Australia. I can understand if it's a bit different coming from different cultures, but you don't often find people complaining about it (in person, online you get all manner of people uninvolved whinging about it)
I fully support your letter and hope massive outrage will force Eye-Fi to give a sustansial discount on a new device. 20% is a bit of and insult.

Laurent Egli
Professional Photographer
President of the USPP Swiss Professional Photographers Association
> Turns out scientists and engineers are still willing to pay for tools.

Free software != Gratis software.
The real question is why in the world you'd move tmp.
That's great, what other courses there are updated ?
They are forced to use it if they want to have subscriptions in the app.
"The TCP standard is evolving, and if you have to always use your kernel's TCP stack, that means you can NEVER EVOLVE." -> This is untrue, the Linux kernel is open source, you could "easily" write your own and replace the current. Either in a branch or trying to get it in the official tree.
Eh. One could argue that the link itself is a "flamewar topic" because it's such a contentious issue.

The Vimeo link I provided is something "genuinely new", I've certainly never seen it here before.

However, I understand that my ad hominems broke HN guidelines.

Carry on.

Trump 2016.

;)
He changed the original statement.

The reason for this for anyone not familiar with colours and pixels is that the Apple P3 primary colour red is a different red from sRGB's. That means that if you do not provide additional metadata, the value will be dumped directly to whatever type of display you are using, making it display the colours using your display's lights.

As other posters have noted, if you view the colour with no colour management system in place, you are instructing the machine to display 241 intensity as is, which means you are seeing (very likely) the sRGB lights in your display set to 241 and 255 intensity; a very easy difference to spot. This is not the intention of his example.

In a colour managed system, that 241 value is transformed into an absolute colour model, and from there it is mapped to the smaller gamut of sRGB. That is, the Apple P3 RGB lights are converted to meaningful sRGB RGB light representations.

So why does an Apple P3 value end up being the "same" sRGB value, despite being different colours? It amounts to a mapping issue.

The entire range of intensity values at 8 bits per pixels for the Apple P3 red channel is an identical colour at all intensity levels. Same goes for sRGB; intensity does not change the colour. When we examine any single P3 intensity, we can map that colour to a "closest possible" sRGB triplet. No matter what we do, the P3 red is different to the sRGB red light, and the sRGB red light can never represent the fully saturated and different red of the Apple P3, no matter what encoded intensity value.

Given that the P3 primary for red is quite different, we end up with a value for sRGB, that after transformation and clipping to the sRGB gamut, is a collision when mapped to sRGB; several different colours might end up mapped to the same sRGB colour due to quantization. In the case of 241, it happens to map to 255 using the rendering intent he selected because some or both of the complimentary values end up negative and clipped in the smaller sRGB gamut. Every other value is also being mapped to sRGB, and there are going to be mapping collisions along the entire intensity range because again, no matter what we do, the sRGB red lights can never represent the red lights of Apple's P3.

An excellent reference on ICC colour management is here for anyone interested, including covering rendering intents and other issues: http://www.cambridgeincolour.com/tutorials/color-space-conve...
>For example a dairy farmer in Switzerland earns more than one in Poland because people pay more for milk products in Switzerland compared to Poland.

A Swiss farmer is much more productive when measured in currency units, but probably not that much in milk volume.

However as we are talking about salary differences it's money that matters.

>So why would the GDP per capita of their country be a useful tool in deciding who to hire?

Why would it be? In this conceptual model the ability of a developer is how much he multiplies the output of whatever he's working on, but his productivity is the absolute value of added output. How could it be counted otherwise, in what? Lines of code?

If productivity didn't depend on location immigration wouldn't exist.
> - Don't you have work to do?
> - Yep, that's why I'm coming back tomorrow again.

Hah, good one.

I'm curious in this toxic situation doesn't it just take a few good companies that treat their employees well to change things around? The good engineers will flock there leaving the bad ones at the old companies.

Granted that probably means the managers will now try and get 2x the work out of the remainders. Maybe some will get a clue though and change their ways.
Not too late to consider a switch to Superfeedr https://blog.superfeedr.com/google-feeds-api-welcome/
Superfeedr https://blog.superfeedr.com/google-feeds-api-welcome/
> The image in question:

> https://webkit.org/blog-files/color-gamut/Webkit-logo-P3.png

> does have a color profile.

I didn't comment on the handling of that image. My comment related to the bit of the article I quoted, which states that WebKit treats images without a color profile as sRGB.
People who focus on color profile support in a world where all colors are compressed to 8 bits per channel with a nonlinear gamma curve are obsessing about the wrong problems. I notice banding artifacts (caused by quantization to 8 bits) and blending issues (caused by linear blending of nonlinear values) way more often than I notice anything related to color gamuts.

People who care about color should be pushing to change the default color representation to a linear format with 16 bits per channel rather than making marginal changes to the edges of 8 bits per channel gamma compressed representations.

That has to start with the addition of 16 bit floating point format support to various hardware. It's really a crying shame that so little hardware supports 16 bit floating point. In addition to imaging it would be useful for audio, and deep learning too.
> This is presumably more money for PBS than they were getting before

Their priority is not profit, but public service. Since this reduces the availability of their programming, it is a disservice to the public that supports them through taxes, regardless of how much richer they are now.
This is a matrimonial site, not a dating site.
For what it's worth, the Third Amendment claims were thrown out:
http://www.reviewjournal.com/news/las-vegas/judge-police-tak...
This is just anecdotal, but it speaks to the technology problem. I live in DC; a few weeks ago, I found myself in a queue with some rather loud young women who all work/worked in a FOIA department of some federal agency (they didn't say which). They spent maybe 15 minutes complaining about various coworkers and their general incompetency. I especially remember their remarks about one man who absolutely could not learn about the redaction feature in Adobe Acrobat. He always printed documents, manually redacted them with a marker, and scanned them again. Not out of any kind of malice--he just couldn't/wouldn't learn a better way.
No agenda. As I stated originally, it's not appropriate to hold up BTC as anything other than an extremely speculative gamble. I simply disagreed with the top post which offered up an "appeal to authority" -- an SEC-sanctioned ETF based on BTC -- that shrouded BTC in an air of 'investability' that is 100% not true. BTC is a horrifically dangerous placement of money. And the problem is, BTC fans -- most of them -- act like they don't know just how risky and speculative BTC is, and its near-zero utility as a medium of exchange.

I'm telling you, get hyper-objective about the danger of converting highly-accepted stores of value into BTC.

For example, most gamblers say to themselves:

"I know I can/will lose money gambling. But my purpose for gambling is not to invest and get a good risk-adjusted return. My objective for gambling is to enjoy the thrill of the process -- and the thrill of gambling is worth more to me than money I can lose."

And many gamblers would add to that by saying "I'm only taking $5000 to Vegas this weekend -- when that's gone, I'm done."

Gamblers view a super-high-risk of loss as paying for a day at DisneyWorld. They lose their money on the day. But the thrill of the rides makes up for it.

My only 'agenda' is BTC users need to understand the risks they're taking. And far too many do not know.

Don't lose money on BTC unless you know you're in it for entertainment -- like going to Vegas or Disneyland -- and that you're fully expecting to lose a lot or all your money.

Just ask this guy -- Kolin Burges, who traveled from England to Japan to confront Mark Karpeles about his missing 200,000 pounds (about $300,000 roughly):

http://i.dailymail.co.uk/i/pix/2014/02/26/article-2568258-1B...
What is wrong with Java/Python? I don't know about Java, but Python is certainly a nice language to write in in my opinion. (However don't expect raw performance from Python.)