Fork me on GitHub
#shadow-cljs
<
2017-09-26
>
Jon04:09:36

in which city?

Jon04:09:24

CoffeeScript has not been updated for long time. Only released 2.0 very recently.

Jon04:09:05

and by using CoffeeScript, it first compiles to ES2015+ , and it has to be compiled with Babel for old browsers.

bolasblack04:09:30

In Shanghai, Caohejing Development Zone

bolasblack04:09:55

I know CoffeeScript released 2.0 recent, but we have given up using CoffeeScript now ๐Ÿ˜‚

bolasblack04:09:51

Because of some JavaScript tools have poor support for CoffeeScript

Jon04:09:21

when did you start using coffee

Jon04:09:48

well... teambition gave up coffee too, very recently

bolasblack04:09:18

I start use coffee from at least 2012โ€ฆโ€ฆMaybe more earlier, I didn't remember

Jon04:09:39

that's even earlier than teambition..

Jon04:09:55

how many people. why never heard of you

bolasblack04:09:28

But my current company start use coffee at 2015 I think...

bolasblack04:09:23

I convince two company to use coffee ๐Ÿ˜›, include current company

Jon04:09:43

teambition started using CoffeeScript in 2013, switched from Python

bolasblack05:09:24

But they are all startup company, so you have not heard of them is normal

Jon05:09:35

but it did not contribute back to the original project, only got to switch to ES6 when they found coffee pooly maintained

Jon05:09:55

teambition was a startup too, at least in 2014, only 20+ people

bolasblack05:09:30

๐Ÿ˜‚ my two company only 10+- people both

bolasblack05:09:23

I'm current working for Pomotodo/Duohui, I think you didn't heard

Jon05:09:30

never heard

Jon05:09:36

Chinese name?

bolasblack05:09:03

็•ช่Œ„ๅœŸ่ฑ†/ๅคšไผš

Jon05:09:45

never heard..

bolasblack05:09:02

I have been hesitant to apply for http://ele.me employees 3 years ago, but I heard that they no longer use CoffeeScript, so I gave up

Jon05:09:39

I don't know..

Jon05:09:57

at least sofish does not like CoffeeScript when I was there

Jon05:09:11

in late 2016

Jon05:09:02

are you in WeChat group? maybe we chat in WeChat...

bolasblack05:09:37

I'm not in WeChat group

Jon05:09:42

200+ members already, although not many Clojure programmers

Jon05:09:48

add me by jiyinyiyong

thheller08:09:44

@bolasblack sorry for the sketchy release quality, just pushed [email protected] which should fix your issues

thheller08:09:02

I compiled your project with the require comments removed

thheller08:09:14

aws-sdk and airtable now work afaict ๐Ÿ˜›

thheller08:09:32

also fixed the cache-root properly

thheller08:09:17

one thing Iโ€™m not too sure about is whether or not I should check if a package exists, that seems somewhat limiting

thheller08:09:48

ie. if you (:require ["airtable" :as ...]) the compiler checks whether node_modules/airtable exists

thheller08:09:07

that really is not required and will break if you installed airtable to global or some other parent path

thheller08:09:17

node will happily find it

thheller08:09:51

I might add a :check-packages true|false option so its less strict

bolasblack08:09:10

I think shadow-cljs needn't check it, because webpack/browserify/(or runtime? user will get an error) will check it ?

thheller08:09:50

yeah, exactly

thheller08:09:24

the only reason it is checking is because CLJS core allows (:require [react ...]) which is a magical symbol that ONLY works if node_modules/react exists

thheller08:09:47

but in case of a string I donโ€™t need to check since I already know that it is a JS dependency

thheller08:09:53

so keep using strings ๐Ÿ˜‰

thheller08:09:18

all the issues you had were due to the check not properly running on some package.json files

bolasblack08:09:25

I even don't know CLJS core support that ๐Ÿ˜‚

bolasblack08:09:38

I tried alpha10, it works very well!

thheller08:09:45

phew finally ๐Ÿ™‚

bolasblack08:09:23

Thanks for your work, shadow-cljs is much much much much better than lein-cljsbuild or boot-cljs for me ๐Ÿ˜‰

thheller08:09:54

and we are just getting started

thheller09:09:25

still need to finish some code before Iโ€™ll post it to the usual sources

thheller09:09:38

but if you guys have some feedback Iโ€™m all ears ๐Ÿ™‚

thheller10:09:02

@jiyinyiyong webpack uses uglifyjs to minify things correct?

Jon10:09:27

do you still prefer a shorter name for shadow-cljs?

thheller10:09:21

not sure, I think I used it too much already to change it

thheller10:09:58

but since it is now able to compile pure JS projects we might need something more generic ๐Ÿ˜‰

Jon10:09:20

updating packages and namespace would be huge work I think

Jon10:09:49

I was suggesting "coleujs" anyway..

thheller10:09:30

yeah I saw .. didnโ€™t like it too much

thheller10:09:01

do I seriously have to replace process.env.NODE_ENV? I thought uglify-js would be able to do that?

Jon14:09:01

playing with my new Macbook... migrating configs

Jon14:09:35

when I was configuring Webpack, I still have to replace that, during bundling for production

Jon14:09:51

Or maybe a name starts with s, I don't think it's as good as col.. though http://www.southernliving.com/plants/s

thheller15:09:54

not worried about the name too much โ€ฆ more important things to do ๐Ÿ˜‰

Jon15:09:22

well, the name is the most interesting part, actually I don't like the "-" in the name.. we have lein-cljs boot-cljs, as a result shadow-cljs sounds like there's a thing called shadow. ๐Ÿ˜‚

thheller16:09:05

hehe just ran react v16 through my bundler

thheller16:09:17

------ WARNING #1 --------------------------------------------------------------
 File: node_modules/react-dom/cjs/react-dom.development.js:1122:2

 unreachable code
--------------------------------------------------------------------------------

------ WARNING #2 --------------------------------------------------------------
 File: node_modules/react-dom/cjs/react-dom.development.js:1155:2

 unreachable code
--------------------------------------------------------------------------------

------ WARNING #3 --------------------------------------------------------------
 File: node_modules/react-dom/cjs/react-dom.development.js:2865:2

 unreachable code
--------------------------------------------------------------------------------

------ WARNING #4 --------------------------------------------------------------
 File: node_modules/react-dom/cjs/react-dom.development.js:12560:4

 unreachable code
--------------------------------------------------------------------------------

------ WARNING #5 --------------------------------------------------------------
 File: node_modules/react-dom/cjs/react-dom.development.js:16870:4

 unreachable code
--------------------------------------------------------------------------------

------ WARNING #6 --------------------------------------------------------------
 File: node_modules/react-dom/cjs/react-dom.development.js:16879:4

 unreachable code
--------------------------------------------------------------------------------

thheller16:09:22

guess I should tell someone ๐Ÿ˜‰

thheller16:09:32

// Flow needs the return null here, but ESLint complains about it.
  // eslint-disable-next-line no-unreachable

thheller16:09:35

guess they know

Jon16:09:55

flow looks good ๐Ÿ˜„