Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment I also warned people (Score 1) 135

I also warned people, that they criticized and hated Flash because of how it was used intrusively by marketers. Pop-over ads, etc. I warned and said that with Flash dead, they would simply turn to HTML5. Except now it would be native, and you'd no longer be able to block their ads. And I was right.

Comment Executive Failure...truly killed Flash (Score 1) 135

The final nail, was when Adobe's own executive exclaimed that he saw HTML5 as the future. When these words were said, Adobe pretty much pointed a shotgun at it's developers and pulled the trigger.

Why did Adobe's CEO say this? Because he was stupid. Even thought true, it was not what a CEO was supposed to do. But Adobe saw HTML5 as their holy grail. They would be able to have their cake and eat it too. They could write tools and take Flash developer and update it to create HTML5 content, and save millions on development of the Flash player.

Business-wise, it was a sweet opportunity from Adobe's viewpoint. However, Adobe hadn't reached that point, and the dumbf*** CEO basically publicly stated this before Adobe had migrated both it's tools and developer base. Imagine if Microsoft decided they were going to cease supporting all .NET/VB/C# and move to Node.js. But haven't released anything to do so yet.

***
The sad thing is that Adobe's Flex team was moving in a really great direction. Meanwhile, HTML5 was released, and in many areas it went "stupid". Sure canvas and all is great. But seriously, adding more input type was the very last thing HTML needed.

Adobe's Flex team realized this with their transition from Flex 3 to Flex 4. Rather than trying to develop new components for every situation (Checkbox, radio, drop down, text input, listbox, etc, etc). They realized a simple fact. Check all the apply and a multi-select listbox are the same data. A radio button and a dropdown is the same data. The presentation is just different. So they went the opposite direction of HTML5, and reduced the input types.

Now you have Boolean, string, list. You could define if the list allowed multiple selection. And you could style the list with a visual layer to be a vertical list, radio buttons, or even a custom skin (thumb images in a grid layout). It was brilliant. They took the revered MVC model and applied it to their input components - something HTML5 should of done.

Meanwhile, their ActionScript 3.x was actually a nice language in many ways. Very similar to Java, but with a few really nice abilities. Properties for example. Forget creating getter and setter methods. Define a property. "MyFoo.color". But hey, what if you have to add a restriction. No problem, there was a getter setter operation for all property elements. So if you later wanted to restrict the colors to 256 color palette, you could add the getter/setter for the property. No need to say MyFoo.setColor or MyFoo.getColor. It was simply MyFoo.color = blue, or display MyFoo.color.

I really wish HTML5 had gone a more intelligent route instead of the stupidity it went. HTML5, should of reduced the number of inputs to Bool, String, List. Then rather than adding new inputs such as phone, url, etc. Added the ability to associate "formatters". A formatter would be similar to a schema definition, that would also denote a preferred keyboard type. Then add keyboards to the HTML5 spec.

So rather than telephone, you'd have a string input with a telephone formatter. The formatter would detail input type "numberic", "9 chars", etc. as well as a preferred keyboard. "keyboard=keypad". Similar a ZIP code, SSN, etc would all merely be strings, restricted to numeric, and default to a keypad keyboard. Sadly, Adobe's Flex team was headed in this beautiful direction. HTML5 went fruit loopy...

Honestly, I said for a while, that Adobe should of released their own webkit browser that did not have security. But simply showed a defined API/Object Model construct that enabled ActionScript to be utilized on the browser DOM. Open source it. Allow all other browsers to incorporate it natively or via plugin. And present ActionScript3 as a "typed" language alternative to JavaScript for browsers.

Had they done this, they would of accomplished much of their goals. While at the same time not shooting themselves and all their developers in the head.

Comment What are you asking for salary? (Score 1) 239

You're on the east coast. I'll presume mid- to north- east. In which case, a decent IT salary would be around the $110K mark. Are you offering anything like that?

How much was your college education? I bet a year with an American salary can pay off most of the Indian educational costs. For an American to get a similar equivalent education, costs a fortune in student loans. As such, an American often needs about 40% more salary to cover those loans than an H1B visa holder. So when you make $65K, and lower the wages of an American down to $65K. You actually get a better standard of living than the local. As they're often paying a large percentage of their income to their student loans.

Comment Sorry BS (Score 1) 239

And if a company like Google can't find an experienced worker in all of America to import. That position should be paid well over a $135,000. That should be a $250,000 position bare minimum.

And the number one way that contracting firms filter out locals from H1B. Wages offered. They'll offer a $65K job in the greater DC/Baltimore region. An American with a family who is unwilling to live in a slum can't afford that low of a wage.

Comment Duh (Score 1) 184

What should of been done ages ago. The amount of space those CRTs took up versus modern flat panels is huge. So there should be a way to take a basic CRT monitor input, create a small device that will receive said signal and convert it to a modern HDMI output. Heck, they can probably even upscale so that while still 8-bit graphics, they will be displayed on a high res screen. This should be the norm.

Comment BS (Score 2) 131

Most contractors don't set prices. They can accept the price or move on. Can't turn down too many customers. Well guess what, you can't go too many days without coding and remain a contractor either. Can't drive whatever car they want. Nope...you need to have a tool that meets a modicum of professionalism. Yes, you're a contractor...but when you go to meetings you are required to dress appropriately...or you lose the privilege of being a contractor.

Comment First off. (Score 1) 131

Nearly EVERY taxi driver is a private contractor. A company owns the cabs, and the licenses. They then lease these out to the cabbies to drive. No benefits. No W2.

Second, why are these laws ignored? I work for a company on a government contract. We have dictated to us: where we sit, what machine we use, and when we have to be there for work.

"Specifying "you may only use DeWalt tools on this contract" can be enough to have your contractors qualify as employees."
But they're not specifying that. They're specifying that you need to have your own tools. And that they need to be contractor grade. You can't show up to work with a Black and Decker drill from Walmart and a battery that lasts 20 minutes. Nothing wrong there.

***

Let's get to the real crux of the matter, W2. I think we need to eliminate the distinction of W2 and contractors. I think we need to eliminate company provided benefits. Shift the entire benefit industry to groups. Trade groups. Regional groups. Whatever.

But let's have honest accounting. No more should our employers pay half the Social Security Tax. We should receive that money, and then we should pay the entire tax. Cause frankly, contractors get abused and the government is never going to protect the individual on those abuses. So let's end that distinction.

Comment Wrong it was not... (Score 1) 405

1. It was note, the photographer even had trouble getting up to the monument.

2. Go look at the link I posted, it clearly visibly debunks the media representation of an empty ceremony.

3. I am not saying Trump's was bigger than Obama's. Just that Trump's was very large too, one of the larger ones in history.

4. Please note that most of the metrics claimed, such as metro transit statistics are meaningless. This was a Republican, most DC residents are not Republicans. Therefore they tend not to use local transit. Most come out of state/district.

Slashdot Top Deals

Quark! Quark! Beware the quantum duck!

Working...