sgdread

> There is no money involved in the Pocket thing.

* It doesn't matter if money are involved or not. Firefox always was a pure browser free of crapware (at least that was a goal: open and free software). Now it is not. The problem is: if one piece of adware is allowed, then there would be another one and in 5 years it will be fully supporting AskToolbar. Just stick to original plan and keep it pure. I bet there will be money involved: I just cancel my donations to Mozilla and send them to EFF instead if this adware won't be removed.

> Pocket was added internally and not as an extension because it was easier.

* It doesn't matter if it was easier if the idea was not right in a first place. According to FirefoxFeedback 92% of requesters asking to remove "feature".

> You don't become a Pocket user simply by using Firefox, you need to actually use the feature.

* Then why it is in the bundle, why it is on toolbar, why I have to perform actions to hide it? Why adBlock plus is not in the bundle (it's waaaay more popular)? Software is good when there's nothing good to remove from it; Pocket and loop (hello) are both not welcomed and not wanted pieces;

> If you don't use it, then it is not doing you any harm. If somehow the presence of a button annoys you, then you can click the "customize" menu item and remove that button.

Until someone will find exploit and create security hole. Removing the button won't remove code from codebase.

> Try to see how partnerships and opportunities make things better for everyone.

I believe it is better for everyone not to include questionable 3rd-party services into FF platform.

There's awesome game which improves twitch reflexes and feels like nice exercise for brain: osu! I usually do this in between active learning to reduce stress. Works like physical exercise.

https://osu.ppy.sh/

>> So, most of the worst radioactive elements are long gone

You're wrong. Just facts:

Cesium-137 half-life 30 years

Strontium-90 half-life 28 years

Enterprise, embedded systems, database development, etc. Not including quantitative analysis/research stuff. If you look at infrastructure of any large company (like Twitter, for instance), their web part is just a tip on top of huge backend iceberg.

I want to point another thing: more and more ISPs are moving away network neutrality. Latest example: Verizon is injecting cookies into users request to be able track their activities and then sell gathered info to advertisers [1] I don't have problems with 3-letter agencies doing what they have to do (though, I would prefer to have proper governance over data access procedures and SSL might help there too), but ISPs should not be altering your traffic. Especially if you pay for the service. SSL prevents cookies injection.

[1] https://www.eff.org/deeplinks/2014/11/verizon-x-uidh

They're more stiff. Same with reds - they're more stiff compared to browns. If you really want to try it yourself, you can order MX switches sampler (something like this: http://www.amazon.com/Max-Keyboard-Keycap-Cherry-Sampler/dp/...).

Here's official statement (got an email from BCBS with same content): http://anthemfacts.com/

The biggest question I have is why such sensitive data was not encrypted.

If you're not going to build tests, you'll spend 4x in debug sessions and also get "fear of change". I worked in a project where we had 80%+ branches coverage in unit tests and awesome automated regression package for end-to-end. When you have that, you have a luxury to be lazy in predictions what would break if I fix this. 90% of defect were business-related, not stability or functionality issues.

You think that 2 days is nothing, but look at this from other perspective: first time MS asks for 2 days (BTW, as others pointed, initially MS said it's not going to be fixed until Feb), next time they ask for a week: last time you gave us 92 days, couldn't you wait for another 3 days? And then it goes, and goes. Then other company asks for a week. If google refuses, there will be unfair treatment and might cause bad press (much worse than this one). So as despite it looked like a dick move, I fully support google's actions. If you compromise on policy once, you're done. So 90 days is a 90 days, no matter what. I think it was a lesson to MS: take this policy with respect and avoid this in future. I'm a software developer and I know how difficult to fix big systems like Windows (burocracy must be crazy there), but the only way to challenge broken processes is to put pressure, otherwise it will never change.

It depends on target. Lasers will work much better against optical sensors (on drones, missiles, etc.).

another complexity is that the plutonium core is not just any weapon-grade plutonium: it has to be casted in unstable delta phase (which has unusually low density; the implosion's task is to switch it into alpha-phase which is much dense: this process makes core critical and explosion happens). Not to mention toxicity of the material itself.

It took me 5 month to get my first Java job (every day 4hrs after work; 8 hours on weekends). And now I see how lucky I was to get that junior position. It took almost year to hone basic Java skills and learn necessary basic stack of technologies to do plain Java projects. It took another year till I got my enterprise stack skills to acceptable level. Every technology/framework is 1-1.5k pages book reading and hours of practice just to start doing something useful. And then you have to repeat that every year, because frameworks updating faster than you can learn, priorities shifting, you forget things.

Edit: However, I must say, ^ was done almost in vacuum: I had noone to ask and had limited access to the Internet (sorry, no Stackoverflow for you :). With good instructors, well-prepared programs and strict discipline in classromms, I would say it is possible to get into entry-level positions.

Tracking issue highlight on EFF: https://www.eff.org/deeplinks/2014/11/verizon-x-uidh

I just wanted to point that ability to display surfaces is not CAD. CAD gives you tools you need to do your job efficiently in specific context.

There're different point of views:

- If you're 3D modeller, then yes, you're operate in terms of splines, surfaces, NURBS curves, etc. 3D model is your product.

- If you're mechanical engineer (and CAD usually appear in engineering context), then in most cases 3D model is just a tool to produce something useful for manufacturing. Engineer models manufacturing process by applying specific primitive operations in specific order(order is important) which will emulate available manufacturing operations (like sweeping, drilling). In other words, when I need to add hole in a part, I don't create surface (or bunch of these - in case if hole intersects other surfaces), I just add extrusion operation; an operation tree will log info "extrusion with diameter 6 at this coordinates from base A and B", not "surface a,b and c". CAD will build all necessary surfaces for me as well as will have all necessary parameter for CNC machine. In 99%* you don't interact directly with surfaces/meshes. At least that's what you do if you work with Autodesk Mechanical Desktop/Autodesk Inventor/SolidWorks/CATIA/Unigraphics.

* 1% are rare cases when you have to deliver something really complex like auto body parts (though making those is a whole new story).

It's a very nice 3d primitives collection, but I don't see how it is CAD (at least in context of mechanical engineering). - First of all, as a mechanical engineer, you're not dealing with surfaces, you're dealing with 3D objects, created using sets of operations: extrusion, revolution, sweep, etc. (ideally you want to reproduce the manufacture process of a part; in some systems then you can export these operations into series of commands for CNC machine). - Secondary, if the output is not CNC machine, it's usually paper. Then the end result of CAD 3D modelling is a series of sections, projections, tools to annotate dimenstions, put tolerances, etc.

Set #7 is much harder than #6. And there're rumors about set #8 which has attacks on EC-algos.

Yep, banks heavily use these to store tickers (currencies, instruments) and do calculations of VWAP, etc. Pretty much standard in the industry for these kind of applications.

What a nice piece of propaganda. Reality though, is different. You, sir, need to research the subject before posting. Lots of army officers, construction workers went there with motivation: "if not us, who?". Slaves won't do what was done there.

Very cool. Worked like a charm. And the best thing in demo: I don't have to register anywhere to try it.

Running IntelliJ 14EAP. Runs like a charm.

Edit: used Eclipse for 6 years, but forced to switch from Eclipse because project grown to a degree that Eclipse can't open it properly (lot of maven cross-dependencies). Another thing: Eclipse 4.x really dropped quality bar - performance is terrible, unstable (compared to 3.8.x).

It was a really nice adventure to complete all the 6 sets. Learned lots of useful stuff. My great thanks to tptacek and the team who prepared such a nice hands-on crypto class. P.S. 7th set is insane (in a good way).

Anything with 64b+ encryption must be reported [1]. Strong encryption is still subject of export restrictions. For example, Java need special unlock to enable encryption 128bits+

[1] https://www.federalregister.gov/articles/2010/06/25/2010-150...

I believe you can use vinegar to treat that.

I've seen same kind of tests on one of the fire ranges. You have to read safety rules. One of the points was to put x mark on the 2nd page if you read that.

JetBrains has really nice tracking tool - youtrack[http://www.jetbrains.com/youtrack/] - free up to 10 people.

I wonder if I can legaly use the drive as an online backup storage (containing "buckets" with client-side encrypted content - mostly photos; encryption will obviously prevent from smart de-duping in the cloud). I was trying to find "fineprint" (like S3 and Amazon Glacier), no luck. It's just too good to be true, I still can't believe the 1Tb has such low price. Another interesting thing: SLA (do they have disaster recovery setup, etc.)

Stock companies require signed model release for every person on the photo. But copyright is belongs to creator - photographer.