點學寫靚PROGRAM

其實python個indent based syntax有d問題,
佢會令到你用唔到editor嘅auto formatting
原因係佢冇close block

寫過下python script,
有時褪錯位真係望好耐先見到點解個loop有d部分淨係最後一次先有行

如果你見其他人寫code褪錯位，會唔會想鬧佢先？

你指python定咩先 梗係會啦

上面有人話可以用OOP設計左個藍圖之後再以FP/IMMUTABLE幫手做implemention，咁我想問其實OOP夾FP變左做stateless之後仲算唔算OOP？

勉強算係掛

因為佢stateless之後佢每次改state都由真改變左return一個新instance比你,
個transform過程都仲算係自己顧自己
其他人同以前一樣都係send message比佢叫佢做野,
只係叫完要接住新嘅佢, 而唔係攬住同一個instance

但呢個真係一個好問題

呢個話題繼續討論落去之前要先定義好咩為之FP
仲有Java8如何使用FP，Java8到底仲係咪OOP

stateless極其量只係immutable, 未同fp有關係住

fp最基本有higher order function,
compose function with functions, currying果類野

我唔熟java, 直接評論唔到

immutable既追求同OOP object with state既觀念都唔同，而且好似岩岩相反添
但問題係immutable之餘點樣做到OOP既好處

其實python個indent based syntax有d問題,
佢會令到你用唔到editor嘅auto formatting
原因係佢冇close block

寫過下python script,
有時褪錯位真係望好耐先見到點解個loop有d部分淨係最後一次先有行

如果你見其他人寫code褪錯位，會唔會想鬧佢先？

你指python定咩先 梗係會啦

Python 個 design philosophy係咁
'There should be one-- and preferably only one --obvious way to do it' 同 'Readability counts'

其實python個indent based syntax有d問題,
佢會令到你用唔到editor嘅auto formatting
原因係佢冇close block

寫過下python script,
有時褪錯位真係望好耐先見到點解個loop有d部分淨係最後一次先有行

如果你見其他人寫code褪錯位，會唔會想鬧佢先？

你指python定咩先 梗係會啦

Python 個 design philosophy係咁
'There should be one-- and preferably only one --obvious way to do it' 同 'Readability counts'

Python教條(Version 1):
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.


Python教條(Version 2):
In the face of ambiguity, refuse the temptation to guess.
There should be one—and preferably only one—obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than right now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea—let's do more of those!

我諗係得Python呢個教派有咁鬼「認真」嘅教條!

其實python個indent based syntax有d問題,
佢會令到你用唔到editor嘅auto formatting
原因係佢冇close block

寫過下python script,
有時褪錯位真係望好耐先見到點解個loop有d部分淨係最後一次先有行

如果你見其他人寫code褪錯位，會唔會想鬧佢先？

你指python定咩先 梗係會啦

Python 個 design philosophy係咁
'There should be one-- and preferably only one --obvious way to do it' 同 'Readability counts'

Python教條(Version 1):
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.


Python教條(Version 2):
In the face of ambiguity, refuse the temptation to guess.
There should be one—and preferably only one—obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than right now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea—let's do more of those!

我諗係得Python呢個教派有咁鬼「認真」嘅教條!

唔熟python唔係好理解
但係好多lang都成間教會咁
golang 都係一隻宗教味好濃嘅prog lang , 佢本身嘅設計已經有好多opinionated style, 仲會同你講, 淨係比一個syntax你用, 咪唔驚見到inconsistency囉
例如佢冇while, 繼續用for keyword, 不過佢唔洗你寫成 for (;condition;) 而係 for condition 就夠
咁前面巴打提到 for (;condition;) 同while 嘅紛爭就消失左
傳統for loop都可以有番齊三格野, 點寫我就唔清楚, 啱啱d go syntax都未必啱

js 教而家唔洗多講添啦

將自己一手一腳寫既程式由零重新寫一次，就會用到有關技巧同改善既地方。

之前學校project做隻OpenGL既氣墊球game，隊友做OpenGL，我用JS寫個game logic比佢port過去。

想知道大家點睇我啲code 睇下可以點樣改進下

( ~200 lines )
https://github.com/mingchoi/air-hockey-physics/blob/master/physics.js

我奇怪你點解唔抽constant? 如果有，又點解唔用UpperCase?

Player.x / PlayerX
Ball.x / BallX 睇到好亂

其實python個indent based syntax有d問題,
佢會令到你用唔到editor嘅auto formatting
原因係佢冇close block

寫過下python script,
有時褪錯位真係望好耐先見到點解個loop有d部分淨係最後一次先有行

用

其實python個indent based syntax有d問題,
佢會令到你用唔到editor嘅auto formatting
原因係佢冇close block

寫過下python script,
有時褪錯位真係望好耐先見到點解個loop有d部分淨係最後一次先有行

用

用vi 個陣比個=G 佢

其實python個indent based syntax有d問題,
佢會令到你用唔到editor嘅auto formatting
原因係佢冇close block

寫過下python script,
有時褪錯位真係望好耐先見到點解個loop有d部分淨係最後一次先有行

用

用vi 個陣比個=G 佢

python咩都fix唔到, 又或者整爛你d code

其實python個indent based syntax有d問題,
佢會令到你用唔到editor嘅auto formatting
原因係佢冇close block

寫過下python script,
有時褪錯位真係望好耐先見到點解個loop有d部分淨係最後一次先有行

用

用vi 個陣比個=G 佢

python咩都fix唔到, 又或者整爛你d code

寫python 用pycharm ， 好好用

其實python個indent based syntax有d問題,
佢會令到你用唔到editor嘅auto formatting
原因係佢冇close block

寫過下python script,
有時褪錯位真係望好耐先見到點解個loop有d部分淨係最後一次先有行

用

用vi 個陣比個=G 佢

python咩都fix唔到, 又或者整爛你d code

寫python 用pycharm ， 好好用

我唔係做python dev
用黎做scripting裝個pycharm貪得意咩