Full title: A data breach at shipping giant Ceva Logistics is rippling across banks, retailers, Steam gamers, and beyond
965 karma · joined February 25, 2015
> That's just not true, and if it is in your case, then you're not great at writing prompts yet.
That's just not true, and if it is in your case, then you're not great at writing code yet.
I'd be very interested in reading more about this. Could you please explain what are these checks and how they are qualitatively and quantitatively better than the default rustc checks?
Please note that this is about checks on the codebase itself - not system/integration tests which are of course already applicable against alternative implementations.
> For example, a typical bilingual speaker of Indian English and Hindi will replace instances of the /æ/ phoneme (as in "blast" or "fast") with another phoneme like /a:/ (as in "father"). Which isn't that unusual since /æ/ is pretty uncommon among languages.
does not apply to Indian languages because most of them have daily-use-words with the /æ/ sound.
It is obvious that historical advancement of technology has caused widespread cultural changes, and a sizable percentage of them are considered negative by a large portion of the population. To state that commercially viable AI could cause such effects as well does not seem necessarily unhinged to me, but in fact worthy of discourse on this forum.
It seems to me that having a huge database of known locations of vehicles could be used to do some cool (but likely immoral) things, specially coupled with the fact that several state agencies all over the world make it free and easy to retrieve licensing and ownership information for vehicles. It'd also be relatively much easier to do compared to facial recognition.
At the end, you get a button to copy some latex, which you are instructed to paste in some website which applies a template and you get a preview back. You can get a PDF as well. Example here https://l.awalgarg.me/oobqng33.pdf.
Seems handy I guess for getting a starting point.
I made this but with markdown a while ago, https://github.com/awalgarg/cv-maker.
Here in India, cyber law enforcement is a joke, and if some legal issue comes up with this site, I'd be curious to see how it works out.
And, just a hypothetical follow up question: how would it work out if the site was not even DMCA compliant?
For parent: check out http://github.com/awalGarg/curl-tap-sh (disclaimer: I am the author, and it was on HN's frontpage already a while ago)
I wrote https://github.com/awalGarg/cv-maker/ which generates the resume in markdown. From there, you can convert it with pandoc to basically whatever you want. It is not much polished yet, though.
Otherwise looks nice, atleast in the images.
I use paper to sketch out thoughts and draw diagrams, and I don't want unlimited papers. 5 pages a day is enough for me. I wish I could say I read books - I don't. So I only have to manage papers on which I write things and refer to them quickly whenever possible. It works fine, but if someone has tips to help, please share. Thanks.
You can have a log of configuration changes for your system, you can have various profiles with branches, etc. Want to switch to a different profile? Just `git checkout <branch-name>`, done! Want to revert some change, or see how your PC looked like 2 months ago? `git log` and `git checkout` your way through!
I currently have all my configurations[1] in a dotfiles directory representing the home directory (same directory structure etc.) and symlinks to them in the actual home directory. Very easy to manage.
The touchbar is on the keyboard, almost perpendicularly (and many times at an obtuse angle) opposite to the screen. So I have to move my head up and down all the time. This is not an issue with the regular keyboard because it has physical buttons which don't change their meaning, so I have memorized the layout and I can use my muscle memory.
To avoid moving human head up and down, maybe they should have put it adjacent below or above the screen, you know. And while they were at it, maybe they should have just merged it into the screen seamlessly... Oh, and while they were at that, they could make the entire screen a touch-screen instead of just a small bar. Just imagine... a touchscreen laptop. Now that would be amazing, right?
I guess we should just hope that engines will optimize their own promise implementations. This might not matter much in front-end apps, but absolutely does for Node apps.
Other than that, I believe it is time JS gets: 1. An actually useful try/catch (with pattern matching on the catched errors) 2. Standard stack traces across all engines
Those two will really help async/await.
> Something you didn't mention: when a Google-car goes around taking pictures for StreetView it also maps the location and all wifi networks name. So taking a new router with a new network name from a different ISP might work, but only until they come near your house to update their pictures... > - Bakuriu
I am not sure how this makes me feel :-|
Thanks.
There is virtual-hyperscript which ports the above to virtual-dom: https://github.com/Matt-Esch/virtual-dom/tree/master/virtual...
I made a similar-ish "library" about an year ago: https://gist.github.com/awalGarg/8a0e18c6fe87456d885f
And there are all sorts of similar DSLs you can find on npm/github for JS. In a bit less time, you can write your own. In even lesser time, you can just do what you used to do prior to all this. This does however seem like a pretty popular idea in the JS community which keeps getting "discovered" every now and then.
> the alternative? [...] install a native app which aren't nearly as well sandboxed right now (Windows, Mac, Linux).
err, the sandboxing works because web APIs don't already expose things which are suggested to be exposed here. Exposing them will break that "sandbox", to a certain (major) degree, atleast.
(x=0)=>_=>++x
the underscore is another variable but a single variable does not require parenthesis. So instead of two chars for the two parens, you use a single char for a single letter variable. JS FTW ;)