Hi, I'm Charles, the founder of codemix [0], we're a distributed team of 4 experienced developers + 1 designer, who're known for delivering very high quality web/mobile apps quickly.
We're based in the UK but we work with companies from all over the world who value our relentless pace and our ruthless user-centric pragmatism.
We focus on shipping quality software and making sure that software truly delivers on its full potential. Sometimes that means us taking on the entire project design/development ourselves and sometimes it means embedding ourselves into a larger team to really drive the project forward.
If you have a project that you need to take to market quickly, and you don't want to compromise on the user experience, I'd love to talk to you about it, email me at [email protected].
In the UK a lot of taxi drivers seem to believe this, the superstition is reinforced whenever they happen to flash when the lights were about to change anyway. It's also a comfort thing, similar to a placebo button[0] - people want to believe that they have some control over the mundane parts of their lives.
The other part is that many attackers see this kind of site as "fair game", compared to more upstanding companies. By its very nature the adult industry attracts the ethically challenged.
Those two examples are really poor, the usability is terrible in both cases, and the effects are not impressive enough to be worth giving up core features like zoom and copy / paste.
Yeah, agreed. I looked at the football one and it reminded me of low quality Flash work circa 2006... until I had to close the tab because I was worried my MacBook Pro was going to melt my glass desk.
I suppose if CoffeeScript were reimplemented from scratch today, it would make sense to compile to an ES6 AST that could be passed on to Babel for further processing and code generation.
Unfortunately, both of those are still very much inferior to TypeScript. I'm waiting for flow to improve enough to actually become usable (still missing basic things like ES6 or really any kind of modules support for type exports, afaik?).
In the meantime, TypeScript works rather well and is looking to add JSX support.
TypeScript is great, but you might look again at flow. ES6 features are being added (I'm adding let/const support) and many already exist. Import/export (incl. types) are in, fat arrow syntax, destructuring, shorthand syntax for objects.
I get the most value of Flow through statically typed React component props, which is usable today with both `React.createClass`-style and `React.Component`-style components.
In my experience, Flow will infer much more about "plainly" written JavaScript than TypeScript, which will fall back to `any` unless code is annotated.
A small example, function types are contravariant in the negative position in Flow, but bivariant in TS—much weaker!
TLDR, if you haven't looked at Flow recently, look again!
Really like the idea of Flow but doesn't look like IDE support is there yet? This is the killer feature of types in Javascript for me - not sure I'd adopt it until then.
I've been testing atom for front-end development in the last few days and it's pretty good, definitely worth checking out (I'm saying this as a vim-lover)
Atom with eslint, the react plugin and eslint-babel is just amazing for ES6/7 and React development. It's so much faster than it used to be, it's actually amazing.
For sure, tooling is an area that will get better over time. I am quite happy with the very simple vim-flow, but TypeScript's tooling and overall ecosystem (tsd/definitelytyped) is a lot more mature.
I will. By the way, I always use TS with --noImplicitAny, and the number of type annotations I've had to add is rather small and very reasonable (mostly just on function arguments of methods and non-lambda functions).
Seems like the flow docs may need an update to reflect the newest additions.
I'm also keen for Flow to improve, but for now it's possible to turn off the `flow` transformer in Babel and pass the compiled output to flow - this preserves type annotations in the output
Macros for JavaScript have been available for a long time[0], you can even use the C preprocessor[1]. Also I wrote a macro plugin for babel just yesterday [2]
Is this sarcasm? io.js would not exist if joyent hadn't made significant mistakes, e.g. failing to ship a new release for years, also this political point scoring alienated a lot of people - https://www.joyent.com/blog/the-power-of-a-pronoun
I use node.js daily, I've never had a problem. Nor have I heard any.
Failing to ship a new release, how is that Joyent's fault? It's core developers who are to blame.
I don't understand the point of the link you sent me. How would a gender neutral alienate people? The person they were talking about here wasn't an employee.
But why would Joyent consider rejecting a PR for gender pronouns as a fireable offense? Probably a website defacement / practical joke.
Edit: FYI - I don't follow this. I don't understand why a fork even exists.
Failing to ship a new release, how is that Joyent's fault? It's core developers who are to blame.
You really are out of the loop. The core developers were frustrated at Joyent not pushing their code, so they jumped ship. Joyent was the steward of the codebase, and they were at fault for not incorporating the developers' work.
How would a gender neutral alienate people?
It's the manner in which they handled the issue that was alienating. Screaming about how tolerant they are, all while screwing over one of their primary contributors, demonising him, and saying he'd be fired rather than retrained. They were soapboxing for cheap political points rather than actually being tolerant and understanding. It's why I actually laughed out loud when you described Joyent as a company that doesn't get involved in politics.
The irony is that the developer in question isn't a native speaker of English, and his native tongue is a gendered language, which likely contributed to his blase attitude on the matter. A little understanding, tolerance, and mature discussion and correction (instead of soapboxing) would have gone a long way.
> But why would Joyent consider rejecting a PR for gender pronouns as a fireable offense? Probably a website defacement / practical joke.
That wasn't a rejection because of gender pronouns. That was a rejection because one pronoun was changed from the docs, instead of all of them. This leads to:
- minor change, not suitable for a PR
- inconsistency, either change all of them to match, or leave them alone
> But why would Joyent consider rejecting a PR for gender pronouns as a fireable offense?
Because community pressure, basically. When there's an angry mob outside about to burn your company down, do you just give them who they want or let your company burn and have everyone else fired too?
Hi, I'm Charles, the founder of codemix [0], we're a distributed team of 4 experienced developers + 1 designer, who're known for delivering very high quality web/mobile apps quickly.
We're based in the UK but we work with companies from all over the world who value our relentless pace and our ruthless user-centric pragmatism.
We focus on shipping quality software and making sure that software truly delivers on its full potential. Sometimes that means us taking on the entire project design/development ourselves and sometimes it means embedding ourselves into a larger team to really drive the project forward.
If you have a project that you need to take to market quickly, and you don't want to compromise on the user experience, I'd love to talk to you about it, email me at [email protected].
[0] http://codemix.com/